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

Re: Bug in creating tar.gz files?

From: Patrick Mayweg <mayweg_at_qint.de>
Date: 2004-05-28 07:50:51 CEST

Hi Branko,
Branko Čibej wrote:

> Ben Reser wrote:
>> On Tue, May 25, 2004 at 09:29:52PM +0100, Barry Scott wrote:
>>> In the subversion-1.0.4.tar.gz there are two top level dirs
>>> subversion/
>>> subversion-1.0.4/
>>> I assume that the subversion/ is a mistake.
>> No you're using a non-POSIX compliant tar program:
>> $ gzip -dc subversion-1.0.4.tar.gz | tar tvf - | grep -E '^subversion/'
>> produces no output. So far we know that mc and WinZip don't comply.
>> When we get to 1.1.0 we'll start doing releases in zip format too
>> because we'll have --native-eol for export.
> I wonder if we really need that. On Windows, the commonly used
> programming editors (UltraEdit, SlickEdit, Visual Studio, Emacs,
> YouNameIt) all handle files with unix EOL correctly, and our .dsp
> generator makes sure the line endings in the project files are
> correct. I always build release binaries from the unixish release
> tarball. We don't _have_ to create another (identical) package which
> differs only in line endings, and it's a nuisance.
> APR needs this because they keep the .dsp's in the tree and refuse to
> disable newline conversion in CVS; so does httpd. We don't.

If we are doing releases in zip format, I would like to have apr-iconv
in there. An important difference between the apache tarballs and zips
is that the zip contains apr-iconv. We need apr-iconv for the windows
build, don't we?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 28 07:51:52 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.