[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Versioning of kdeinit libraries
From:       Thiago Macieira <thiago () kde ! org>
Date:       2007-12-17 20:38:11
Message-ID: 200712171838.12304.thiago () kde ! org
[Download RAW message or body]


Modestas Vainius wrote:
>Hi,
>
>Currently kdeinit libraries (plugins?) in KDE4 (and similary in KDE3)
> are named as libkdeinit4_{name}.so The problem is that this name (and
> therefore SONAME) is unversioned in general sence (i.e. does not follow
> *.so.{version} notation), but those kdeinit libraries get installed to
> public library location (e.g. /usr/lib). Since recently such
> configuration has been discouraged in Debian.

kdeinit modules are tied to the application, which "reserve" the name 
in /usr/bin. They don't need versioning.

>1) Move libkdeinit* to private location (e.g. /usr/lib/kde4). I think,
> it's not viable because there are "dummy kdeinit executables" linking
> against them.
>
>2) Another solution would be to properly version kdeinit libraries. I
> was thinking if it was possible to add SOVERSION for all kdeinit
> libraries so libkdeinit* stuff would end up like (kdelibs case):

No. They don't need to be versioned because they don't cause clashes or 
co-installability problems. Besides, the "4" in kdeinit4 is the version 
already.

>Would this change have any negative side effects and what do you think
>about it? Any other ideas?

Your patch does not include the changes to the code that loads those 
libraries. It's also several months late -- I guess we don't want to 
change that anymore so close to the release.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]