[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fwd: Version of _nc_write_object symbol
|
From: |
Thomas Dickey |
|
Subject: |
Fwd: Version of _nc_write_object symbol |
|
Date: |
Sun, 11 Oct 2015 13:01:01 -0400 (EDT) |
hmm - "reply to all"...
----- Forwarded Message -----
From: "Thomas Dickey" <address@hidden>
To: "Sven Joachim" <address@hidden>
Sent: Sunday, October 11, 2015 1:00:23 PM
Subject: Re: Version of _nc_write_object symbol
----- Original Message -----
| From: "Sven Joachim" <address@hidden>
| To: address@hidden
| Sent: Sunday, October 11, 2015 12:54:44 PM
| Subject: Version of _nc_write_object symbol
|
| The 20150905 patchlevel introduced a new symbol _nc_write_object
| tagged
| with the version NCURSES_TIC_6.0.current. I assume that's not the final
| version, but is it same to assume that it won't change before a 6.1
prerelease?
yes - I'm uncertain of the best way to evolve this, but in this case I did the
same process as I did for the 5.9/6.0 development, by marking new symbols as
"current", and when I got to the end of 5.9 changes, changing "current" to a
specific patch-date.
| I'm asking because the Debian packaging separates programs and
| libraries, and I don't want to allow combinations of ncurses-bin and
| libtinfo5 that lead to a situation where tic(1) is broken.
--
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net
--
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net