Mail Archives: cygwin/2001/11/02/21:41:08
On Sat, 2001-11-03 at 13:30, Christopher Faylor wrote:
> 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.
That may be it. Setup isn't great at handling those deltas right 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.
Did you bump the suffix number? That should be bumped if changing from
.gz to .bz2.
> Is there something here that 'upset' should be checking for?
Yes please, if you can that would be great. The rule is that
foo-1.tar.gz cannot be replaced with foo-1.tar.bz2, but can be replaced
with foo-2.tar.bz2.
> 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?
The categories release will handle it thanks to Pavel, the HEAD code
doesn't, and may or may not depending on what the streams code ends up
doing.
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -