This is the mail archive of the
cygwin-patches@cygwin.com
mailing list for the Cygwin project.
Re: [PATCH] setup.exe & different archives for the same version of the app
- To: cygwin at cygwin dot com, cygwin-patches at cygwin dot com
- Subject: Re: [PATCH] setup.exe & different archives for the same version of the app
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Fri, 2 Nov 2001 21:30:46 -0500
- References: <NFBBIBMBMMAMDPDHMKEBKEBACBAA.ronald@minisat.com> <1004694386.6940.56.camel@lifelesswks> <3BE2AE80.EAF3FC24@syntrex.com> <3BE2DF9D.7080100@ece.gatech.edu> <1004744567.9086.61.camel@lifelesswks>
- Reply-To: cygwin-patches at cygwin dot com
On Sat, Nov 03, 2001 at 10:58:48AM +1100, Robert Collins wrote:
>On Sat, 2001-11-03 at 05:02, Charles Wilson wrote:
>> <grumpy old-man voice>
>> 2. If somebody changed packaging from .gz to .bz2 without bumping the
>> release number, it was a mistake. Easily fixable -- maintainer should
>> release new version.
>
>Actually, they need to delete the old one completely, or else it'll
>still be there (and confused) in prev. But yes I agree.
I've lost the thread here.
Was there a specific package that this happened to? I did this for
cygwin-1.3.2 without changing the -n suffix. I didn't realize at the
time that this would cause a problem but I can't believe that we'd
be worrying about this now.
I also moved newlib-man out of the cygwin directory and into its own
directory. I didn't change the suffix there either, but I've just done
that as well. I also recompressed it as .bz2 from .gz.
Is there something here that 'upset' should be checking for? Should I
be issuing a warning if a file suddenly changes from .gz to .bz2? Or,
is the new code in setup.exe going to handle that automatically?
cgf