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

Re: [PATCH] new property 'svn:tarballs'

From: SteveKing <steveking_at_gmx.ch>
Date: 2003-07-13 11:09:05 CEST

----- Original Message -----
From: "Ben Collins-Sussman" <sussman@collab.net>
> > > Subversion is not a build system. It's a way to version source code.
> svn:externals is a feature-match to cvs's "modules". It allows you to
> build a working copy that is a mixture of version-controlled
> projects. I admit that it's "on the borderline" of being a bit too
> much for a version control system, but it *is* managing version
> controlled data. My feeling is that when the system starts managing

So you say that if CVS would have such a feature then you wouldn't
mind having it in subversion too? :)

> unversioned data, it has "crossed the line". It's become a build
> tool, not a versioning tool.
> Many tools have crossed this line already: for example, clearcase has
> its own 'make' program. It scares me.

Why does this scare you? I don't know clearcase at all, but
I guess that you're not forced to use the build tool but it's

I don't think its about the definition what "source control" is but
what people expect from a source control tool. If you stick
strictly to a theoretical definition then you'll forget about the
users who actually have to use it.

And yes, many features could be done with other tools
too - but then you could do source control without any
special tool too. The whole idea of source control systems
is to make the life and work of the users easier - no matter
how this is done.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 13 11:11:50 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.