Re: Incompatible changes in the next version of rsyncrypto

[Robin L. P. <rlp...@di...>]

On Mon, Oct 13, 2008 at 11:33:20AM +0200, Shachar Shemesh wrote:
> Hi all,
> 
> This is a heads up, as well as a chance for you to give some
> input, about two incompatible changes I'm planning for the next
> version of rsyncrypto.
> 
> The first change has to do with the "--file-list" option, that
> allows giving a list of files to be processed. At the moment,
> --file-list is a parameter less option, and it merely changes the
> meaning of the first argument from being the actual source file,
> to being a list of files that are used as source. If the first
> argument is "-", this means that the list is read from standard
> input.
> 
> The problem begins when the --name-encrypt option is used for
> either decryption or encryption. With this option, the directory
> in relation to which the names are interpreted is crucial. The
> current scheme leave no other option than "the current directory".
> However, asking the client to change the current directory as part
> of the program's arguments seems a bit of an onus requirement.
> 
> The change I am planning is to have --file-list accept a single
> parameter saying "which file to use", with "-" meaning stdin as
> before. The first argument to rsyncrypto will now be the directory
> in relation to which the names given in the file list are
> interpreted.

That will break my scripts.  It's also the right thing to do.  Go
for it!

-Robin

-- 
They say:  "The first AIs will be built by the military as weapons."
And I'm thinking:  "Does it even occur to you to try for something
other than the default outcome?" -- http://shorl.com/tydruhedufogre
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/