ncurses 5.3 backwards compatibility

[Chris Zubrzycki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was wondering why the major number for the ncurses libraries stayed 
the same since you removed some elements from the interface. Upon 
upgrading, a number of apps now break, including ettercap,  lynx and 
hexcurse. (although some like nano an aatest still work.)

here are the errors from lynx:
lynx undefined reference to _acs_map expected to be defined in 
/sw/lib/libncurses.dylib.5
lynx undefined reference to _strfnames expected to be defined in 
/sw/lib/libncurses.dylib.5
lynx undefined reference to _strnames expected to be defined in 
/sw/lib/libncurses.dylib.5

I work with the fink project on Mac OS X, so I cannot put ncurses 5.3 
into fink for everyone to use unless it is 100% compatible. are these 
bugs, or what? I read the faq and release notes, and saw nothing about 
breaking binary compatibility. Thanks guys, ncurses is still great :-)

What would be the best solution? Should I just do #define acs_map 
_nc_acs_map and such to the ncurses src so all our existing programs 
will still run? I know that 5.3 will not be accepted by the project 
lead unless it is 100% binary compatible, or the major version number 
changes so we can have both versions installed.

- -chris zubrzycki
- - --
PGP public key: http://homepage.mac.com/beren/publickey.txt
ID: 0xA2ABC070
Fingerprint: 26B0 BA6B A409 FA83 42B3  1688 FBF9 8232 A2AB C070
========================================================

"Sadly, text alone cannot convey the depths of my sarcasm."

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (Darwin)

iD8DBQE9y+fV+/mCMqKrwHARAvV/AKCQdoPAD+Bkn7OckpAvSunr0WipGgCgl8R1
22kp9Yw1YQ2fQPBCzQ5pdvY=
=TIIk
-----END PGP SIGNATURE-----