> > In a non-SVNParentPath setup, the user specifies a descriptive
> > repository name with the SVNReposName directive.
> Well, no they don't. Ok, now I'm just being rude :-)...
> But I don't at least, for any of the 10 repositories that I
Yes, but you can, if *needed*. I mean, a project may have a pretty
long name that would not fit for a directory name, but could be set as
> Since we've never heard anyone complain about the lack of
> SVNReposName, perhaps a good bet would be that the feature is pretty
> useless and should just be removed? The repository name would then
> always be 1:1 with the name of the folder that contains it.
Same as before. You may need to set a more friendly repository name.
> If the SVNReposName property is actually useful for anything, it is
> at least obviously misplaced in the Apache config file. It should
> instead live in a per-repository config file where it would be
> insensitive to issues such as whether repositories are enumerated
> with SVNPath or SVNParentPath.
+1 here. We could move this kind of setting to some kind of
per-repository configuration file.
> I appreciate that you're working on fixing stuff. I'm just
> wondering why all the complexity, why not just say let's do things
> this way and *always* pick the name out of the URI...
It's the first patch I ever submitted to the Subversion project, and I
don't feel like breaking what has been done so far because it's a very
high quality job. I just figured that there was a good reason for
making the directory name and the directory path two different things.
This patch is just an "add-on" that makes mod_dav_svn able to provide
the repository directory name as the repository name for XML browsing
because of the lack of an explicit repository name.
Of course, if we decide to use a configuration file, I'll be very
pleased to spend some time hacking on this.
Maxime Petazzoni (http://www.bulix.org)
-- gone crazy, back soon. leave message.
Received on Wed Jan 18 00:26:57 2006