> I don't see how. Proxy behaviour should be completely independent of the
> actual client used.
They still can be - just store them in the config files instead of the
registry.
> Yes, they are used, but your patch changed only the registry path -- it
> didn't change the config file name. And config file settings override
> registry settings.
That's the wanted behaviour - so each program can store its own settings
in the registry and if the user wants global settings then use the config
files.
> Well of course, but library versioning deals with that. Mutually
> incompatible libraries will have different names. As for supporting
> older repositories -- hopefully, after 1.0 the schema won't change as
> often as it does now; and the recommended way to deal with schema
> changes will always be "svnadmin dump old-repo | svnadmin load new-repo".
Have you ever talked with an administrator about such things? Usually they
(and me too) don't want to switch over to a completely new version from one
minute to the other. So having different versions for some time is needed
and
the switch is then done when it is absolutely sure that the new version
works
as wanted and as soon as ALL users have the new client installed.
Or are you capable of updating ~100 or more clients within one day? And
teach every user the new client?
> Ah, I think you're looking at Windows only, right? Yes, at the moment,
> we only build static libraries on Windows. This will change, and by
> default we'll be creating DLLs. Also, the library version will be
> encoded in the DLL name, just as it is on Unix.
That's a good idea and surely needed. But no reason to not commit the patch.
> I did agree that having a way to pull settings from elsewhere at runtime
> would be useful. I just don't agree that your patch is the right way to
> do it.
What other way as easy as this do you suggest?
> >and that's something I want to avoid - what belongs together should be
> >stored together!
> But your patch does exactly the opposite.
Huh? How that?
What I expect from a program (no matter what it does) is that it comes with
an installer and ALL files/libraries it might need. I really HATE it when a
program
forces me to download several other libraries from different places and
install them
separately. I know that's the default on Linux but on Windows I expect an
easy
installation (and so do others). So: a client for Subversion needs all
libraries and
helper programs included. As soon as you use more than one client (e.g. a
plugin
for an IDE and a standalone one) you will have different libraries stored in
different
places and the last one installed forces to use the other clients those
libraries (because
those are global settings).
I really, really want to avoid that!
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 5 18:28:50 2002