OK.
Quickly analysing what options are available, a solution is to allow
the user to specify a file used for service name <-> repository path
mapping.
Using access files and svnserve.conf files suppose that the server
already know where repositories are.
Ionel
Le 22 sept. 06 à 17:22, Garrett Rooney a écrit :
> On 9/22/06, Ionel GARDAIS <igardais@yahoo.fr> wrote:
>> Isn't it because a user does not care about where the server is that
>> the server itself should use zeroconf (at least for internal-running
>> servers) ?
>> Sysadmin guys could migrate svnserve from servers to servers without
>> telling end-users.
>
> Sure, and having zeroconf advertise the location of the server is
> certainly helpful, but the user still has to go talk to someone to
> find out the path of the repos and the path of the project within the
> repos. It just seems like you're only solving part of the "How do I
> check out the code to project X" problem, when it should be possible
> to solve more of it.
>
> -garrett
___________________________________________________________________________
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 22 18:10:49 2006