[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 16:07:16 CEST

----- Original Message -----
From: "Philip Martin" <philip@codematters.co.uk>
> I'm not all that keen on svn:tarballs, but I'm not all that keen on
> svn:externals either. Is anyone using svn:externals? Is it much
> better than doing the same thing outside the client (manually or via a
> script)?

We do. We put all the smaller libraries which are used by our
main project in separate repositories and then pull them in
with svn:externals. To make that feature really usefull we would
need issue 1258 (http://subversion.tigris.org/issues/show_bug.cgi?id=1258).
But that has been put post-1.0.

I really can't understand why so many functions and features
people want get dismissed with "you can do that with scripts
or manually". This happens IMHO too often. If I really wanted
to use scripts I don't have to use subversion or any other
version control system: all that could be done with scripts too.
The whole idea of having a source control system is that
all those functions are packed together in one single package
which doesn't need too much tweaking to set up.

Just think about any commercial product out there (not
only version control systems). If for example the famous
photoshop would only have the most essential functions
implemented and all other not so essential ones needed
separate installation or even own implementing (i.e.
programming a script) - do you really think it would
have become such a success? I don't think so.

The same applies to version control systems. I really
don't like it if I have to read several files of a project
to gather all the information where to get the all the
libraries and sources which are needed too. Or worse
if every new project member has to ask the project leader
first where the hell all those libraries are saved on
the companies fileserver. The svn:externals feature
helps a lot with this - just check out the project and
you have all the libraries you need too. And the
svn:tarballs feature would help in those cases where
the external libraries are not under subversion control
or even _can't_ be under version control for whatever

I'm sorry but I'm in a very bad mood today. It seems
that everything I try and everything I do for subversion
gets rejected for reasons I just can't understand. Examples?
No problem:

- a patch to make subversion build as a windows dll the
  same way apr does it.
  Got rejected because some people rather wanted a
  script to do it - the script isn't even started and I wonder
  if subversion will ever compile to a dll.
- a patch for a subversion/apr bug on windows98/Me.
  This bug makes subversion fail on those systems if
  authentication is needed. Got rejected because some
  people wanted subversion rather to report the bug
  instead of working around it.
  -> Once I know about a bug I don't need to be
  told about it everytime I try to use a program. Instead
  I expect the program to work.

And now I'm going outside walking in the woods.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 13 16:08:10 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.