FS#41663 - [ncurses] Apply upstream updates to ncurses
Attached to Project:
Arch Linux
Opened by Steven Honeyman (stevenhoneyman) - Saturday, 23 August 2014, 09:36 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 09 November 2014, 11:23 GMT
Opened by Steven Honeyman (stevenhoneyman) - Saturday, 23 August 2014, 09:36 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 09 November 2014, 11:23 GMT
|
Details
Description:
This version from the GNU site hasn't been updated since 2011, but upstream has been updating it since then - but still having a version number of 5.9 Additional info: ftp://invisible-island.net/ncurses/current/ |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Sunday, 09 November 2014, 11:23 GMT
Reason for closing: Fixed
Additional comments about closing: ncurses 5.9_20141101-1
Sunday, 09 November 2014, 11:23 GMT
Reason for closing: Fixed
Additional comments about closing: ncurses 5.9_20141101-1
http://invisible-island.net/ncurses/NEWS-contents.html
https://packages.debian.org/jessie/libncurses5-dev
I've compiled the latest release, it seems fine (so far!)
I guess we will need upstream opinion on this.
They're using them, as 5.9 still
You're right, hopefully upstream will be able to provide a definite answer.
Steven, are you going to contact upstream about it?
In the mean time, there is an interesting program I didn't know existed: "abi-compliance-checker" [1]
The report it made says yes, it is compatible. I've attached it.
[1] https://github.com/lvc/abi-compliance-checker
> whether current snapshots are ABI compatible with the latest stable version?
yes - but: there are a few applications which are bit by the change to output buffering
(down in the "unspecified" realm...).
> If there are plans to release a newer "stable" release?
my plan for a stable release is to finish the mingw port (the bulk of the library isn't going to change for that)
[1] http://repo.bpiotrowski.pl/brtln-testing/