On Mon, Jun 10, 2013 at 11:41:12AM +0200, Emilio Pozuelo Monfort wrote:
> You really should read [1] if you're maintaining shared libraries in Debian
> (it's a bit outdated but most things are still relevant). [2] is also a good
> read, specially if you're doing upstream development, patching the l
On 10/06/13 01:04, Jerome BENOIT wrote:
> Hello List,
>
> I am not so sure what I must understand by `bump the SONAME':
> given that libtool machinery is employed, does is mean that
> `current' must be increased by one ?
You really should read [1] if you're maintaining shared libraries in Debian
http://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
On Mon, Jun 10, 2013 at 1:04 AM, Jerome BENOIT wrote:
> Hello List,
>
> I am not so sure what I must understand by `bump the SONAME':
> given that libtool machinery is employed, does is mean that
> `current' must be
Hello List,
I am not so sure what I must understand by `bump the SONAME':
given that libtool machinery is employed, does is mean that
`current' must be increased by one ?
Thanks in advance,
Jerome
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe
On 09/06/13 12:53, Emilio Pozuelo Monfort wrote:
> On 09/06/13 08:00, Jerome BENOIT wrote:
>> Hello List,
>>
>> because of backward incompatibility I have to add a suffix to
>> my library package name. But lintian keep noticing the mismatch.
>> I know the the soname of a library can be specify by
On 09/06/13 13:12, Christoph Egger wrote:
> Emilio Pozuelo Monfort writes:
>> Patching a library downstream to bump the SONAME needs to be done only in
>> very
>> special cases and when you know what you're doing. For instance you're going
>> to
>> break compatibility with third party software t
Emilio Pozuelo Monfort writes:
> Patching a library downstream to bump the SONAME needs to be done only in very
> special cases and when you know what you're doing. For instance you're going
> to
> break compatibility with third party software that links against the old
> SONAME.
Well you also
On 09/06/13 08:00, Jerome BENOIT wrote:
> Hello List,
>
> because of backward incompatibility I have to add a suffix to
> my library package name. But lintian keep noticing the mismatch.
> I know the the soname of a library can be specify by passing
> appropriate options to the gcc tools: is a DH
Thank you both for your quick answer.
On 09/06/13 08:29, Chow Loong Jin wrote:
> On Sun, Jun 09, 2013 at 08:00:39AM +0200, Jerome BENOIT wrote:
>> Hello List,
>>
>> because of backward incompatibility I have to add a suffix to
>> my library package name. But lintian keep noticing the mismatch.
>>
On Sun, Jun 09, 2013 at 08:00:39AM +0200, Jerome BENOIT wrote:
> Hello List,
>
> because of backward incompatibility I have to add a suffix to
> my library package name. But lintian keep noticing the mismatch.
> I know the the soname of a library can be specify by passing
> appropriate options to
Changing package name is not enough. You should patch the library
build system to produce different soname and library filename
2013/6/9, Jerome BENOIT :
> Hello List,
>
> because of backward incompatibility I have to add a suffix to
> my library package name. But lintian keep noticing the mismatc
Hello List,
because of backward incompatibility I have to add a suffix to
my library package name. But lintian keep noticing the mismatch.
I know the the soname of a library can be specify by passing
appropriate options to the gcc tools: is a DH way to do so ?
Thanks in advance,
Jerome
--
To U
12 matches
Mail list logo
