Armin K. wrote:
> On 03/02/2014 09:29 AM, Bruce Dubbs wrote:
>> Alice Wonder wrote:
>>> On Sun, 2014-03-02 at 03:06 +0100, Armin K. wrote:
>>>
>>>>
>>>> It is. Package ships *.la file that depends on another *.la file which
>>>> no package ships that the former one depends on. Packaging error.
>>>
>>> Indeed, Fedora quite some time ago stopped shipping libtool .la files
>>> because of how frequently they were flat out wrong and the dependency
>>> issues they caused.
>>>
>>> To be honest life is just fine without them. pkgconfig does a better job
>>> at the same thing.
>>>
>>> I hope I wasn't going off-topic on the point, but .la files are fragile
>>> and cause issues especially when you are doing fancy stuff like using a
>>> DESTDIR option to make install.
>>>
>>> For LFS where you typically are building locally they probably are fine
>>> but for package managers, they should not be packaged and pkgconfig
>>> should be used instead.
>>
>> You are right about all of this, but the .la files are created and
>> installed by the upstream make files.  They have to be manually removed
>> periodically.
>>
>> Unfortunately, at least one program (gstreamer IIRC) uses .la files at
>> run time to dynamically load modules.  That complicates the process of
>> removing them.
>>
>>     -- Bruce
>>
>
> Not gstreamer. Only two packages I have ever installed use them at runtime.
>
> ImageMagick (only ones in /usr/lib/ImageMagick*/modules*/)
> libgphoto2 (only ones in /usr/lib/libgphoto*/)
>
> /usr/lib*/*.la files can always be removed, those cause nothing but trouble.

Yes, that was what I was looking for:

find /usr/lib* /usr/local/lib /opt -name \*.la | grep -v 
/usr/lib/ImageMagic |grep -v /usr/lib/libgphoto | xargs rm

I got 1425 entries, but I have some older directories contributing:

/opt/{qt-5.1.0,qt-5.1.1,xorg.old,kde-4.10.3,kde-4.11.0,kde-4.11.2,qt-4.8.5.old} 
   :)

   -- Bruce

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to