Hosting a book on Seaside with

Ken Causey ken at
Tue May 9 19:57:54 UTC 2006

OK, perhaps I misstated myself.  What I should have said is one
'repository' per project, not one directory.  In other words if your
project were to be called 'seasidebook' then I or Marcus would:

svnadmin create --fs-type fsfs /home/svn/site/seasidebook (and some
other stuff not relevant for this discussion)

That would completely seperate each project wouldn't it?  Sorry for the


On Tue, 2006-05-09 at 21:51 +0200, Damien Cassou wrote:
> Ken Causey a écrit :
> > I'm curious what you mean.  I was just assuming that we would have a
> > directory per project where each project would then be responsible for
> > their own sub-tree structure.  Does that sound overly messy to you?
> > Perhaps I don't understand your point.
> As a svn user, I agree with this. One directory for every project cause 
> a lot of problems:
> - Each project share the same revision number (ie: you won't have 
> following version numbers for your project)
> - It's more difficult to manage hook scripts (sending a mail on each 
> commit for example)
> - It may be more difficult to manage read/write access
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :

More information about the Squeak-dev mailing list