Re: Building a shared library with no SONAME

2019-02-08 Thread Domenico Andreoli
On Wed, Feb 06, 2019 at 12:26:24PM -0500, Nicolas Mora wrote: > Le 2019-02-06 11:59, Andrey Rahmatullin a écrit : > > It's a bad idea to package shared libraries that don't keep stable ABI. > > > [...] > > > Please don't just add a random SONAME. Library versions with different > > ABIs must have

Re: Building a shared library with no SONAME

2019-02-06 Thread Nicolas Mora
Le 2019-02-06 11:59, Andrey Rahmatullin a écrit : It's a bad idea to package shared libraries that don't keep stable ABI. [...] Please don't just add a random SONAME. Library versions with different ABIs must have different SONAMEs so if you add a custom SONAME you will need to change it each

Re: Building a shared library with no SONAME

2019-02-06 Thread Andrey Rahmatullin
On Wed, Feb 06, 2019 at 11:19:21AM -0500, Nicolas Mora wrote: > I'm currently packaging libgraphqlparser > (https://github.com/graphql/libgraphqlparser) which is a library for parsing > graphql queries. > > Currently, the cmake script file doesn't add the SONAME to the shared > library, leading to

Building a shared library with no SONAME

2019-02-06 Thread Nicolas Mora
Hello, I'm currently packaging libgraphqlparser (https://github.com/graphql/libgraphqlparser) which is a library for parsing graphql queries. Currently, the cmake script file doesn't add the SONAME to the shared library, leading to lintian warning: https://lintian.debian.org/tags/shlib-with