[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: Jeff Stuart <jstuart_at_computer-city.net>
Date: 2003-07-15 23:35:29 CEST

On Sun, 13 Jul 2003 11:09:05 +0200
"SteveKing" <steveking@gmx.ch> wrote:

> ----- Original Message -----
> From: "Ben Collins-Sussman" <sussman@collab.net>
> >
> > > > Subversion is not a build system. It's a way to version source code.
> So you say that if CVS would have such a feature then you wouldn't
> mind having it in subversion too? :)

While I'm NOT a subversion developer, chances are yes, IF CVS HAD that
feature, then yes, SVN WOULD have copied it as SVN from the ground up is
designed to be a replacement for CVS.

> 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.

A) This is the Unix philosphy in practice. IE Use the right tool for the job.
   And use shell scripts to GLUE two or more tools together. SVN IS just
   about source code control. Make IS just about being a build system. Use
   the right tool for the right job.

B) The whole idea of source control systems is IMNSHO to provide developers
   with version management of code files.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 15 23:36:20 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.