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

Re: svn commit: r13838 - branches/1.1.x

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2005-04-03 01:44:31 CEST

--On Saturday, April 2, 2005 2:46 PM -0600 kfogel@collab.net wrote:

> [I realize this may be asking you to repeat stuff you've already said
> in IRC.]
> Are such releases made often, and for purposes that we want to
> support? In general, I agree that we should be using released
> tarballs only for our own releases (sounds like no one disagrees on
> that point).
> I don't feel like having the export code in there is a huge deal
> either way, but I'd like to understand the justification better.

The issue here is that creating a tarball for your own purposes would be,
IMHO, overly complicated if you had to find and extract release tarballs of
all the dependencies. Creating a 'private distribution' (or limited-release
distribution; which I used to do back in the day to package releases to some
clients and users) would be streamlined by just exporting from the upstream

I think having dist.sh capable of running the svn export lessens the overhead
required to get a tarball out the door. For public releases, we can state
that the RM must use extracted tarballs. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 3 01:45:58 2005

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