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

List:       gimp-print-devel
Subject:    Re: [Gimp-print-devel] linking specific gimp-print
From:       Kai-Uwe Behrmann <ku.b () gmx ! de>
Date:       2004-06-01 6:55:30
Message-ID: Pine.LNX.4.44.0406010853110.1989-100000 () sirius ! rasena
[Download RAW message or body]

Roger,

I take it as an distribution misbehaviour and will point this out this
way.

thanks
Kai-Uwe


Am 30.05.04, 21:42 +0100 schrieb Roger Leigh:

> Kai-Uwe Behrmann <ku.b@gmx.de> writes:
>
> > Am 29.05.04, 00:42 +0100 schrieb Roger Leigh:
> >
> >> The libgimpprint.so symlink is pointing to the wrong library.  This is
> >> probably because 4.2.x was installed after the 5.0.0-alpha version and
> >
> > 4.2.x first and 5.0.0 was installed afterward.
>
> Did you use the same --prefix?  /usr/lib/libgimpprint.so should point
> to /usr/lib/libgimpprint-5.0.0-alpha3.so if "make install" was used to
> install.
>
> >> replaced the correct symlink.  This isn't a problem specific to
> >> gimpprint--it will occur for all libraries, except for e.g. gtk and
> >> gnome, which put the major and minor version in the soname.
> >>
> >> We could put the specific version in the .pc file for development
> >> versions, but since it wouldn't be done for a stable release I don't
> >> think we should be doing this for the beta releases and onwards.
> >> Also, once we have both stable and development releases which contain
> >> .pc files the .pc files will be overwritten just like the symlink, and
> >> you're back to square one.  The best solution is to just have one
> >> version of the headers/.so symlink/.pc file installed at once, or at
> >> least installed in different prefixes.
> >
> > Installed the SuSE-8.2 libgimpprint-4.3.3-21.rpm including
> > /usr/lib/gimpprint.so . This is an system folder. Many other libs and
> > applications rely on it like standard gs.
> >
> > Maybe I run into an distribution problem, together with others.
>
> If the library package includes the symlink, the package is buggy.  It
> should live in a -devel package.  The symlink is only required for
> linking, not running.  For example, on Debian there is:
>
> libgimpprint1             - 4.2.x libgimpprint.so.1 library
> libgimpprint-5.0.0-alpha3 - 5.0.0-alpha3 libgimpprint-5.0.0-alpha3s.so
>                             library, modules and data
> libgimpprint-dev          - virtual package providing headers and
>                             libgimpprint.so symlink
>
> You can have as many library packages installed as you like, but there
> can only be one development package (headers + symlink) installed at
> once.
>
>
> --
> Roger Leigh
>
>                 Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
>                 GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.
>



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
[prev in list] [next in list] [prev in thread] [next in thread]