setup: empty tarballs

setup: empty tarballs

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

There's been quite a bit of back-and-forth over setup.exe's handling of
empty tarballs.  What has actually been implemented?


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkizWpgACgkQpiWmPGlmQSPVsACfR+AgizWCsdSn3TjA4sQCvnzE
CBQAniZM/6f5TxjvhOemlVe4v/4DZJHf
=hM/v
-----END PGP SIGNATURE-----

Re: setup: empty tarballs

[Corinna Vinschen]

On Aug 25 20:21, Yaakov (Cygwin Ports) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> There's been quite a bit of back-and-forth over setup.exe's handling of
> empty tarballs.  What has actually been implemented?

Setup.exe for 1.5 is unchanged, afaik.  I tweaked setup for 1.7 (CVS HEAD)
so that it shouldn't complain anymore about any type of empty tar file.
I have no idea if there was a decision to prefer a certain type of
empty tar archive.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Re: setup: empty tarballs

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Corinna Vinschen wrote:
> Setup.exe for 1.5 is unchanged, afaik.

Yeah, I noticed.  Annoying, too. :-(

> I tweaked setup for 1.7 (CVS HEAD) so that it shouldn't complain 
> anymore about any type of empty tar file.
> I have no idea if there was a decision to prefer a certain type of
> empty tar archive.

OK; FYI right now cygport is producing 14-byte tarballs.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEUEAREIAAYFAki18ggACgkQpiWmPGlmQSNgjQCeMdRvHXlHpd3k60bENXMj7ILj
11sAlj2iFNIFG4sXz1SglDQA9nSKOx0=
=7UAW
-----END PGP SIGNATURE-----

RE: setup: empty tarballs

[Dave Korn]

Corinna Vinschen wrote on 26 August 2008 08:57:

> On Aug 25 20:21, Yaakov (Cygwin Ports) wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>> 
>> There's been quite a bit of back-and-forth over setup.exe's handling of
>> empty tarballs.  What has actually been implemented?
> 
> Setup.exe for 1.5 is unchanged, afaik.  I tweaked setup for 1.7 (CVS HEAD)
> so that it shouldn't complain anymore about any type of empty tar file.
> I have no idea if there was a decision to prefer a certain type of
> empty tar archive.

  The thread was "setup.exe: Invalid or unsupported tar format", starting Mon
05/05/2008 21:24.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....