Hi!
While CVS - through its concept of modules - somewhat dictated the use of the repository, Subversion doesn't do this. Standardising on repository layout for all of clo has some advantages though: if you decide to do that, it will be possible for example to provide a standard hook script to update the project website when a change is committed for it.
There are several possibilities to standardise on (taking cl-irc as an example):
First: / cl-irc/ trunk/ branches/ tags/ public_html/
Second: / cl-irc/ trunk/ public_html/ branches/ tags/
Third: / trunk/ cl-irc/ public_html/ branches/ tags/
The third option is the layout you get when converting the existing cl-irc repository using cvs2svn. In my opinion, it's the least favorable, since normally tags and branches are created with copies from trunk, meaning all modules get tagged at the same time...
The second option wouldn't be my favorite either, since, dist scripts would then package the website (unless special action is taken not to). I don't think websites belong in a dist tarball.
The first option would be my favorite, since I don't think of a website as something needing tags and branches. This setup allows for separate tags for all modules, which is quite sane in my opinion.
That's all folks!
Oh, well, if you decide which you want to standardise on (remember: 3 is what you get when converting from CVS), I don't mind writing the hook.
bye,
Erik.
On 1/26/06, Erik Huelsmann ehuels@gmail.com wrote:
While CVS - through its concept of modules - somewhat dictated the use of the repository, Subversion doesn't do this. Standardising on repository layout for all of clo has some advantages though: if you decide to do that, it will be possible for example to provide a standard hook script to update the project website when a change is committed for it.
This is a nice idea but now that I think about how few projects currently check in their public_html in CVS I think it's unlikely they will care about doing the same in Subversion. Right now the Subversion repositories are pretty empty; we could choose to set up branch, tag, trunk as a default of course. That wouldn't be bad. Are there any "camps" inside the Subversion community that doesn't like the trunk, tag, branch setup and prefer something else?
Thanks, Erik.
Hi
I have become quite a fan of subversion and I am happy to see c.l.net supporting it.
I have gone back and forth about repository layout and I kind of favor the second layout if I understood what you mean. Bau maybe I didn't.
What is the public_html directory? Is it the documentation of the cl-irc project?
Cheers -- Marco
On Jan 26, 2006, at 4:16 PM, Erik Huelsmann wrote:
Hi!
While CVS - through its concept of modules - somewhat dictated the use of the repository, Subversion doesn't do this. Standardising on repository layout for all of clo has some advantages though: if you decide to do that, it will be possible for example to provide a standard hook script to update the project website when a change is committed for it.
There are several possibilities to standardise on (taking cl-irc as an example):
First: / cl-irc/ trunk/ branches/ tags/ public_html/
Second: / cl-irc/ trunk/ public_html/ branches/ tags/
Third: / trunk/ cl-irc/ public_html/ branches/ tags/
The third option is the layout you get when converting the existing cl-irc repository using cvs2svn. In my opinion, it's the least favorable, since normally tags and branches are created with copies from trunk, meaning all modules get tagged at the same time...
The second option wouldn't be my favorite either, since, dist scripts would then package the website (unless special action is taken not to). I don't think websites belong in a dist tarball.
The first option would be my favorite, since I don't think of a website as something needing tags and branches. This setup allows for separate tags for all modules, which is quite sane in my opinion.
That's all folks!
Oh, well, if you decide which you want to standardise on (remember: 3 is what you get when converting from CVS), I don't mind writing the hook.
bye,
Erik. _______________________________________________ clo-devel mailing list clo-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/clo-devel
-- Marco Antoniotti http://bioinformatics.nyu.edu/~marcoxa NYU Courant Bioinformatics Group tel. +1 - 212 - 998 3488 715 Broadway 10th FL fax. +1 - 212 - 998 3484 New York, NY, 10003, U.S.A.
On 1/27/06, Marco Antoniotti marcoxa@cs.nyu.edu wrote:
What is the public_html directory? Is it the documentation of the cl-irc project?
Every project has a /project/<project-name>/public_html directory. Whatever you put in there is what shows up as http://common-lisp.net/project/<project-name>. In addition, many projects add their public_html directory as a module in their repositories so it's versioned.
Erik.
-
Erik Enge -
Erik Huelsmann -
Marco Antoniotti