[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: gcc source management requirements

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2002-12-10 03:12:23 CET

On Monday, December 9, 2002, at 08:44 PM, sam th wrote:

> In a discussion with Tom Lord on the GCC list, Zack Weinberg [1] posted
> an excellent list of requirements for a source control system. Some of
> them are for the future, some of them are requirements for anything
> that
> wants to replace CVS. They're worth taking a look at. [2]
> http://gcc.gnu.org/ml/gcc/2002-12/msg00444.html
> [1] Who I know is on this list, but hasn't mentioned his list on this
> list. Hope I'm not stepping on your toes, Zack.
> [2] It should be noted that SVN fails requirement 0. Hopefully the APR
> people consider this an issue as well.

well, which part of requirement 0 are you talking about? i don't
believe we fail the portability part, at least for a client build
(although for some of the more obscure platforms it remains to be

we definately fail the "anonymous access doesn't need a userid that can
write to the repos" test, since you need write access to open the
berkeley db files that make up the filesystem, so apache (and
mod_dav_svn) must be running as the user who owns the repos.

certainly we also fail the reliability portion, but that's largely
because the system hasn't had time to mature. as more people use it,
more and more bugs get shaken out of it. given time, i have no doubt
we will hit that requirement as well.

we also fail parts of 2, but that's just because we've chosen not to
deal with them until after 1.0.

everything else (i think) we pass (or intend to pass by the time we hit
1.0), modulo the occasional bug of course.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 10 03:13:21 2002

This is an archived mail posted to the Subversion Dev mailing list.