On Nov 21, 2004, at 9:09 AM, Stas Bekman wrote:

It should be something like (1):

http://svn.apache.org/viewcvs.cgi/perl/modperl-docs
http://svn.apache.org/viewcvs.cgi/perl/modperl-2.0
http://svn.apache.org/viewcvs.cgi/perl/modperl-1.0

If we are planning to do a different nesting to accomodate other projects it could be (2):

http://svn.apache.org/viewcvs.cgi/perl/modperl/docs
http://svn.apache.org/viewcvs.cgi/perl/modperl/2.0
http://svn.apache.org/viewcvs.cgi/perl/modperl/1.0
http://svn.apache.org/viewcvs.cgi/perl/embperl/1.0
http://svn.apache.org/viewcvs.cgi/perl/embperl/2.0

I agree that these would be a lot more clear and meaningful, although you *should* have a "trunk" directory in there somewhere. I like these:


https://svn.apache.org/trunk/perl/modperl/docs
https://svn.apache.org/trunk/perl/modperl/2.x
https://svn.apache.org/trunk/perl/modperl/1.x
https://svn.apache.org/trunk/perl/embperl/1.x
https://svn.apache.org/trunk/perl/embperl/2.x

But this is also okay:

https://svn.apache.org/perl/modperl/docs/trunk
https://svn.apache.org/perl/modperl/2.x/trunk
https://svn.apache.org/perl/modperl/1.x/trunk
https://svn.apache.org/perl/embperl/1.x/trunk
https://svn.apache.org/perl/embperl/2.x/trunk

Of course, whenever you crete a branch, it would have to look something like this:

https://svn.apache.org/perl/modperl/2.x/branches/branch_name

Likewise for tags, it would have to be:

https://svn.apache.org/perl/modperl/2.x/tags/tag_name

For the first example they would have to be like this:

https://svn.apache.org/branches/branch_name/perl/modperl/2.x
https://svn.apache.org/tags/tags_name/perl/modperl/2.x

Which I have to say, given the multiproject nature of the Apache svn installation, probably makes less sense.

More on repository layout and the ideas behind it is documented here:

  http://svnbook.red-bean.com/en/1.1/ch04s07.html#svn-ch-4-sect-7.1

Regards,

David


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to