Hey all
Ubuntu 16.04 ships libjson-c2, Debian Stretch ships libjson-c3.
The externals from purest_json from Deken link against libjson-c.so.2 and thus do not work in Debian Stretch. I only discovered that after I removed "obsolete" packages (packages that were installed from previous releases and were not removed during upgrade).
Now I wonder: Is it possible as a Deken package maintainer to take care of this situation gracefully? Currently, you get packages from Deken that cannot work on some systems.
Roman
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi,
On 25.04.2018 09:25, Roman Haefeli wrote:
Hey all
Ubuntu 16.04 ships libjson-c2, Debian Stretch ships libjson-c3.
The externals from purest_json from Deken link against libjson-c.so.2 and thus do not work in Debian Stretch. I only discovered that after I removed "obsolete" packages (packages that were installed from previous releases and were not removed during upgrade).
Now I wonder: Is it possible as a Deken package maintainer to take care of this situation gracefully? Currently, you get packages from Deken that cannot work on some systems.
I am not sure how to fix that, only by either statically linking all dependencies or including shared libraries in the deken files. I am opposing both ideas, but I have no real solution for that.
Any other ideas? Thomas - -- "Theoretically, [the amount of money in circulation] is watched carefully by clever, serious economists. In practice, all the world's money is one big swirling, whirling pool." (Cory Doctorow - For The Win) http://www.residuum.org/