On Wed, May 24, 2017 at 09:14:48AM +0200, Libor Pechacek wrote:
On Wed 24-05-17 08:07:00, Dr. Werner Fink wrote:
Yes Sir, it does!
... only the question rises how to enforce this in the autobuild system?!
I'm not an expert in packaging hence will not provide a detailed answer. However, it's clear that libncurses6 package must not provide the old symbols so that the incompatibility is detected at package installation phase. That will also trigger the (auto)build (service) package refresh.
On NetBSD I could use something like libncursesw.so.6 kernel.ostype Linux:libtinfow.so.6,libncursesw.so.6 in /etc/ld.so.conf.d/ncurses.conf ... but this is not specified on Linux AFAIK ... ? Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr