rpms/gtkdatabox/devel gtkdatabox.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2

[Michael Schwendt]

On Fri, 11 Aug 2006 07:50:22 -0700, Chris Weyl wrote:

> > > %post -p /sbin/ldconfig
> > > %postun -p /sbin/ldconfig
> > > %post devel -p /sbin/ldconfig
> > > %postun devel -p /sbin/ldconfig
> >
> > The scriptlets for the -devel package are not needed. When the package is
> > installed, the *.so symlink points to the right *.so.N library file
> > already. In case the *.so.N library has been replaced with a different N,
> > you're in trouble anyway, and updating the link with ldconfig would lead
> > to unexpected/wrong results (i.e. -lgtkdatabox would not link with the
> > library from your main gtkdatabox file).
> 
> Wouldn't that conflict with:

No.
 
> "MUST: If the package contains shared library files located in the
> dynamic linker's default paths, that package must call ldconfig in
> %post and %postun. If the package has multiple subpackages with
> libraries, each subpackage should also have a %post/%postun section
> that calls /sbin/ldconfig."

The -devel is a sub-package, *but* it doesn't contain any library.

It contains only a symbolic link to a file contained within the
main package. A symlink only to be used during compile-time.

The paragraph you quoted refers to real library files which shall enter
the dynamic linker's search cache.

I recommend the paragraph is rewritten:

  "MUST: Every binary RPM package, which stores shared library files
  (and not just symbolic links) in any of the dynamic linker's default
  paths, must call ldconfig in %post and %postun.

> In this case, there is a versioned .so[1] present in the main package,
> with an unversioned library in -devel, per guidelines.  There isn't a
> symlink from the unversioned to the versioned being created.

The symlink is included in the -devel package.