RFC: adding a temporary, non-BC gauranteed, 'private' library .. where?

[Alex Merry]

On Thursday 23 April 2009 20:49:39 Alexander Neundorf wrote:
> On Thursday 23 April 2009, Aaron J. Seigo wrote:
> ...
>
> > and the headers? that's really my big question. protecting symbols is
> > easy, a policy on where to put such headers is less clear to me.
>
> Maybe install them to share/something/ and require apps using them to copy
> them into their build dir at build time ?
> (uh, oh, that sounds ugly...)
> Or install them as a .tgz ?
> (so the apps can't just do -I<prefix>/share/something/ )

That won't solve the issue that upgrading kdelibs (using a package manager) 
will remove the .so files, and so break any applications using the library.

Installing the headers is fine, as long as the library is in a separate 
package (from kdelibs).

Alex


-- 
Why have I got six monitors?  Because I haven't got room for eight.
  -- Terry Pratchett

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090423/238cdb43/attachment.sig>