package _version_ check

[Charles Wilson]

> gdbm-1.8.3-7
> libbz2_0-1.0.2-1
> libgdbm-1.8.0-5
> libgdbm3-1.8.3-3
> libintl-0.10.38-3
> libintl1-0.10.40-1
> libncurses5-5.2-1
> libncurses6-5.2-8
> libreadline4-4.1-2
> libtiff3-3.6.0-2

These are mine.

> it would be very nice if the above packages were re-built against 1.5

No, I don't think so.  With one exception, those are ALL compatibility 
packages.  Even if they DID use the functions that were upgraded in 
1.5.x, they STILL wouldn't be rebuilt.  All new apps and libraries 
should be linking against the current libs, which WERE rebuilt:

libbz2_1
libintl2
libncurses7
libreadline5
libtiff4

gdbm-1.8.3-7 **IS** the rebuilt package.  It contains, however:
   /usr/bin/dumpgdbm-1.3.22.exe
   /usr/bin/loadgdbm-1.3.22.exe
which were compiled statically on a stock 1.3.22-only system.  They are 
used to -- yes, you guessed it -- provide backward compatibility and 
migration support.

In the future, don't rely on a script to do your thinking for you. 
Also, you might consider scanning the @#!#%!# cygwin-announce mailing 
list archives.  I didn't spend hours composing 30-odd detailed announce 
messages -- ALL OF WHICH include 1.5.3-compatibility/requirement info -- 
for my health...  Basically, any package which was announced in the 
flurry after cygwin-1.5.3 was released was a 1.5.3 rebuild.

Further, cgf is correct:  OLD programs will continue to run, without the 
64bit functionality, seamlessly on a 1.5.3 system.  Only the newly 
recompiled apps, IF they access the new functions, won't be able to run 
on a 1.3.22 system.  But that's almost always true with any new release 
of the kernel.

--
Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/