[cl-debian] Bug#486376: [Ecls-list] Bug#486376: Bug#486376: ecl: /usr/lib/libecl.so doesn't provide a SONAME

[Luca Capello]

Hi Juanjo!

On Wed, 03 Sep 2008 17:41:25 +0200, Juan Jose Garcia-Ripoll wrote:
> On Wed, Sep 3, 2008 at 4:12 PM, Luca Capello <luca at pca.it> wrote:
>>> That is not something ECL has to provide. It is more a configuration
>>> option that operating systems may provide.
>>
>> Sorry, I'm not a skilled programmed, but I don't understand why this is
>> not ECL task: ECL provides the libecl.so library, so who else should
>> provide its SONAME?
>
> The SONAME is a basically a linker option and can be passed to ECL as
> a configuration flag during the build process. It is not our task as
> developers of ECL to impose a certain numbering scheme or link flags
> on the main source distribution, but rather the package maintainer to
> set it based on their own criteria or distribution standards.

Well, I really think SONAME's decision belongs to developers, not to
package maintainers.  Let's say that Debian uses a SONAME of 0.1 while
Ubuntu 0.2 [1]: then every effort done with the LSB [2] is lost.

I consider this as the last solution and if I'm really forced to
implement it, the ECL SONAME in Debian will reflect the upstream
version.

> At least this is how I have seen that done for other packages,
> including Debian's ones (http://packages.debian.org/etch/libgc1c2) and
> that is what I meant by the text above.

The libgc1c2 package in etch already uses upstream SONAME [3]:

--8<---------------cut here---------------start------------->8---
libgc (1:6.2+6.3alpha1-1) unstable; urgency=low

  * New upstream release (closes: #197031)
  * Switch to using upstream's autoconf (and therefore upstream's sonames, so
    rename packages to match the sonames)  (closes: #178869)
  * Relibtoolize.

 -- Ryan Murray <rmurray at debian.org>  Mon, 11 Aug 2003 15:57:57 -0700
--8<---------------cut here---------------end--------------->8---

Thx, bye,
Gismo / Luca

Footnotes: 
[1] and yes, I compared Debian and Ubuntu *in purpose*, since while the
    latter syncs with Debian before every freeze, in some areas they
    diverge quite a lot
[2] http://www.linuxfoundation.org/en/LSB
[3] http://packages.debian.org/changelogs/pool/main/libg/libgc/libgc_6.8-1/changelog
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 314 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20080906/62601822/attachment.sig>