rpms/libsigsegv/FC-4 .cvsignore, 1.2, 1.3 libsigsegv.spec, 1.5, 1.6 sources, 1.2, 1.3

[Michael Schwendt]

On Fri, 07 Oct 2005 16:34:14 +0200, Ralf Corsepius wrote:

> On Fri, 2005-10-07 at 07:20 -0500, Rex Dieter wrote:
> > Ralf Corsepius wrote:
> > > On Thu, 2005-10-06 at 14:24 -0400, Rex Dieter wrote:
> > > 
> > >>Author: rdieter
> > >>
> > >>Update of /cvs/extras/rpms/libsigsegv/FC-4
> > 
> > >>+rm -f $RPM_BUILD_ROOT%{_libdir}/lib*.la
> > >>+
> > > 
> > >  
> > > You can't remove *.la from a package which already has been released.
> > > This breaks all packages depending on this library. You can only do this
> > > for unreleased packages, but not for already released packages.
> > 
> > I think you're being a bit overly dramatic.
> No. If a package ships an *.la's these are part of these packages' API.
> RH is ill-advised in removing them and so is FE.

Unfortunately, libtool archives are less beneficial than they do damage at
build-time. They inflate the build requirements with lots of inter-library
dependencies which are not used directly within an API. Linux's run-time
dynamic linker doesn't need them unless an old libltdl is involved.