[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: devel package for only two symlinks?



On Sat, 21 Oct 2006 20:01:59 +0200, Christoph Wickert wrote:

> Am Samstag, den 21.10.2006, 18:27 +0200 schrieb Michael Schwendt:
> > On Sat, 21 Oct 2006 16:23:46 +0200, Ralf Corsepius wrote:
> > 
> > > On Sat, 2006-10-21 at 16:20 +0200, Christoph Wickert wrote:
> > > > Am Samstag, den 21.10.2006, 16:08 +0200 schrieb Patrice Dumas:
> > > > > On Sat, Oct 21, 2006 at 03:42:41PM +0200, Christoph Wickert wrote:
> > > > > > 
> > > > > > But I doubt this doesn't make much sense for symlinks, does it?
> > > > > 
> > > > > It makes only sense for symlinks... 
> > > > 
> > > > Yeah, sorry, I know. What i wanted to ask is: Do we really need a devel
> > > > package for these two symlinks. I read your answer an a "yes".
> > >
> > > If these libs are libraries: yes, definitely.
> > 
> > Where's the API then?
> > 
> > Unless I misread Christoph's question, there are _only_ two symlinks,
> > but not headers. In that case, something is broken terribly.
> > 
> > In case this is a library without a public API, it doesn't make sense
> > to put the .so symlinks into a separate -devel package. It must be examined
> > whether the .so "names" are needed at run-time, e.g. for dlopen.
> > 
> > So, what package is this about?
> 
> It's from the hylafax review,
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188542

Oh, hylafax indeed. Then you must include them in the main package,
because "rpm --query --requires hylafax" lists them.

The SONAME of the library files does not contain a version (search the
build log for "soname"). Hylafax is linked against "libfaxutil.so" and
"libfaxserver.so" and requires them at run-time. It is an upstream bug
(well, misconception) that the *.so symlinks point to versioned library
file names, which are not accessed directly.

[It is also not good that the non-versioned *.so libraries are installed
into run-time linker's default search path and use a generic name that is
not in "hylafax" namespace. Any "libfaxutil-devel" package would conflict
with the *.so links in "hylafax" even if it used a much lower/higher
library version.]


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]