If the la file is in a plugin dir, it is not correctly detected. The static lib is removed correctly * Removing unnecessary /usr/share/opt/google/chrome/resources/zeitgeist_plugin/plugin/libzeitgeist-npapi-plugin.a ... /var/tmp/portage/gnome-extra/zeitgeist-datasources-0.8.0.1/image/usr/share/opt/google/chrome/resources/zeitgeist_plugin/plugin /var/tmp/portage/gnome-extra/zeitgeist-datasources-0.8.0.1/image/usr/share/opt/google/chrome/resources/zeitgeist_plugin/plugin/libzeitgeist-npapi-plugin.so /var/tmp/portage/gnome-extra/zeitgeist-datasources-0.8.0.1/image/usr/share/opt/google/chrome/resources/zeitgeist_plugin/plugin/libzeitgeist-npapi-plugin.la
Um?
Er, /usr/share/opt? What's that? *nm*
(In reply to comment #2) > Er, /usr/share/opt? What's that? *nm* That was why I was writing the ebuild. Some path had to be corrected. Nevertheless the static archive was removed but the la file not.
And how can it know which plugin loaders use .la files and which do not?
Does any use la files? I thought it is only need for linking.
Unfortunately some obscure software may still need .la files for loading plugins at runtime. imagemagick being one example.
I thought, plugin loaders never need la files. But I was obviously wrong. And as I am against a bunch of special variables to trigger specific actions for individual loader, I would suggest to leave this cleaning to the ebuild maintainers. Thanks guys, -> invalid.