Daniel Rall wrote:
> On Fri, 16 Feb 2007, Garrett Rooney wrote:
>> On 2/16/07, C. Michael Pilato <email@example.com> wrote:
>>> While documenting svnsync in The Book, a question occurred to me. I see
>>> that svnsync has --username and --password command-line options, as well as
>>> the related --no-auth-cache and --non-interactive options.
>>> But what happens if both the source and target repositories of your
>>> mirroring process require authentication, and as different users? Are you
>>> just out of luck in terms of getting non-interactive functionality? Is
>>> a shortcoming of svnsync, or am I overlooking something?
>>> (I admit it -- I haven't tested this to see what happens. It's 4am, and
>>> going cross-eyed, so this mail is as much a TODO that will wind up back in
>>> my Inbox as it is a question for someone else to answer.)
>> If I had to guess it won't work, but like you I haven't actually tried it.
> Sounds like a bug to me. We'd need a second set of
> --username/--password command-line options to correct this problem.
I was thinking the same thing.
Now, how do we do that compatibly? I mean, ideally, the option names would
all carry the "from/to" or "source"/"target" or "source"/"sync" (haha!)
naming. But we already have flat --username/--password.
The best thing I can think of which let's us look forward without changing
the meanings of things today is:
* introduce the four new options
* make "--username FOO" mean "--from-username FOO --to-username FOO";
same for the password args
* only allow --username if neither --from-username nor --to-username
are present (to discourage less-than-clear meanings); same for the
Anybody partial to a particular pair of new option prefixes? I kinda like
"source" and "sync" myself (so --source-username, --sync-username, etc.
It's cute, yet clear.
C. Michael Pilato <firstname.lastname@example.org>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Sat Feb 17 20:09:18 2007