Red Hat Bugzilla – Bug 171503
Last modified: 2007-11-30 17:11:15 EST
You can safely omit packaging those pesky libtool archives from
BTW, were you intending on submitting digikamimageplugins and/or kipi-plugins?
If not, I can submit them soon for review.
kipi-plugins reviewed and imported into cvs.
digikamimageplugins is submitted and under review, but is blocking on this bug .
See bug #171505.
I'm not intending on submitting digikamimageplugins or kipi-plugins.
Is excluding .la files realy safe, I'm asking because of bug #165616 Comment #16
and Comment #17, also https://bugs.kde.org/show_bug.cgi?id=93359
"It has been noticed that Imlib2, a library which uses libtool's API for loading
plugins at run-time, fails in Digikam 0.7"
"When called from within Digikam, which is a KDE application and linked against
libkdecore, Imlib2's plugin loader fails to
find its *.so files, because the libltdl included with KDE is not built with
support for .so files."
digikam's inclusion of /usr/lib/lib*.la files (or not) has nothing to with that
other kdelibs bug. In short, they're safe to remove (or I wouldn't have asked
for it). (-:
More precisely, libtool archives for shared libraries, ie, those matching
are usually superfluous and can safely be removed.
libtool archives for loadable modules, ie, those matching
*sometimes* need their .la counterparts (especially when the aforementioned
kdelibs bug hasn't been fixed, see also bug #171544
Exclude libdigikam.la, packages will appear soon.