[ANNOUNCEMENT] Updated: bzip2-1.0.2-1

Charles Wilson cwilson@ece.gatech.edu
Wed Apr 10 10:28:00 GMT 2002

Randall R Schulz wrote:

> Say what?
> This package showed up at Mirrors.rcn.net yesterday, 

Hmm...I didn't even upload the files until just after midnight EDT 
Wednesday morning (and announced it simultaneously). That's some pretty 
fast mirroring...see way below.

> and I downloaded 
> and installed it without incident or complaint using the 
> previous-generation Setup.exe (

Right -- previous generation setup didn't support dependencies.  So, you 
didn't install the 'libbz2_0' package, on which bzip2 now depends 
(sortof, see below).  It's actually the libbz2_0 package that old 
setup.exe's will be confused by.  Since you didn't even try to install 
it (no automatic dependencies), then you didn't have any problems. 
Until you try to run a program that needs cygbz21.0.dll.

(below): However, the actual executables in the bzip2 package were 
linked STATICALLY for precisely this reason -- so that folks like you 
wouldn't have problems.  In fact, the "dependency" of the bzip2 package 
on the libbz2_0 package is fiction; nothing in the bzip2 package needs 
the dll -- except for the import library.

And any programs that individual users may have compiled PREVIOUSLY that 
they linked dynamically against the OLD bzip2 package's cygbz21.0.dll.

Trust me: all of these gyrations are necessary, including splitting 
bzip2-1.0.1-6 into two separate packages (bzip2-1.0.2-1 and 
libbz2_0-1.0.2-1), so that I can migrate bzip2 to the auto-import build 
style.  That will greatly simplify things...but this step had to happen 

Unfortunately, I ran into some problems with the package name, 
setup.exe, and the fact the "libbz2" -- the official library name of the 
bzip2 package -- ends in a numeral.  On cygwin, I've been naming the 
"DLL-only" packages with a traling numeral that indicates the DLL major 
version (this allows peaceful coexistence and backward compatibility: 
see libreadline4/libreadline5,  libncurses5/libncurses6, etc.)

libbz20-1.0.2-1  ?  looks like twenty, to me
libbz2-0-1.0.2-1 ? oops, setup will parse the '0' as the source version, 
and 1.0.2 as the release version, and the -1 gets thrown away.

So, we settled on libbz2_0 -- but old setup.exe's treated '_' and '-' 
the same.  New setup.exe's do NOT use '_' as a parsing separator. 

libbz2_0-1.0.2-1 ==> packagename=libbz2_0  version=1.0.2  release=1

which is what I needed.  However, old setup.exe's will be confused...

> By the way, if this sort of dire warning is associated with a new 
> release, shouldn't the announcement go out before the package itself?

way below: It did.  However, the gateway between cygwin-announce@ and 
cygwin@ has been broken since Sunday.  Chris is working on it.  But, 
when I noticed that it wasn't working, I resent the announcement 
directly to cygwin@ by hand; unfortunately I didn't do that manual 
intervention last night, but this noon.  Sorry.


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/

More information about the Cygwin mailing list