On Feb 18, 2005, at 2:55 AM, Philippe Auphelle wrote:
> Anyway, since that's not the way svn works, and since we are still in
> the study phase, I guess we'll have to either do with it or stick with
CVS allows remote users to effortlessly create new repositories on the
server? That's news to me. ;-)
>> Maybe a better idea is: make one big repository. Users can start new
>> projects by creating new directories in the repository.
> We considered that, but from what I know of svn (please correct me if
> I'm wrong), we are worried by at least three aspects:
> 1) It goes against the rule of thumb (FAQ) that says "If the projects
> are related, and are likely to share data, then it's best to create one
> repository with several subdirectory". Here, lotsa projects are small
Projects that live in a single repository don't *have* to share data.
It just opens up the possibility, that's all.
> 2) Any straight repository checkout will bring the whole repository
> while just a specific project (subdir) is actually needed
Well, duh... don't checkout the root of the repository. (That's always
a horrible idea, since you'd end up getting a copy of every branch and
Remember that 'svn checkout' takes a URL argument. Every project would
still have a unique URL, whether they all live in separate repositories
or in one big repository.
> 3) Separate repositories insures against inadvertent alteration of the
> tree for project A by someone working on unrelated project B.
"Inadvertent alteration"? That's why access control exists. And
besides, even if somebody accidentally commits to the wrong place, you
just undo the change. That's the whole point of version control,
I think you're inventing imaginary problems here. :-)
Look at the ASF repository: http://svn.apache.org/repos/asf
Dozens of projects living in one repository, happily ignoring each
other. Once in a great while, a project gets renamed, or moved from
the "incubator" area to a full-fledged project. No problems at all.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Feb 18 14:46:02 2005