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

Re: pax built test tarballs

From: Ben Reser <ben_at_reser.org>
Date: 2004-04-05 19:05:27 CEST

On Mon, Apr 05, 2004 at 08:16:23AM -0500, kfogel@collab.net wrote:
> Wow. I think I'm more confused than before that answer, even :-).
> How does the zipping method imply any changes other than the zipping
> method? Is there something about zipfiles that forces us to make
> changes to the software being packaged?

When we discussed doing zip files everyone seemed to agree that the text
files should have CRLF line endings in them. Right now we can produce
zip files on the RM's machine with InfoZip more than likely. But
there's no easy way to handle getting their contents into CRLF format.

I wrote a patch to make export accept an option to set the line ending
marker that you want to use for files marked native. Which makes doing
this very easy. However, this change requires an API change to
svn_client_export() which means we can't do it until 1.1.0.

> Not sure how using trunk for the release solves the problem (but that
> may be because I don't understand what the problem is). Anyway, we
> Shouldn't Go There. Releases for all platforms should come from the
> release branch, except for testing releases which are not meant for
> long-term distribution.

I just meant using trunk to do the export from the branch. Basically
we'd have to roll the zip file by hand. But we'd need the command line
client that will be in trunk as soon as I get around to committing the
change (which I haven't done yet, I need to look at the comments that I
got over the weekend).

Ben Reser <ben@reser.org>
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 5 19:05:44 2004

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.