Hi, > There is a problem in your argumentation. Whereas it does not make sense > to > specify implicit dependencies for shared libraries it does for static > libraries. Even if you don't use a specific library directly it might be > a > requirement to link to this specific library when using static libraries > because another library you are using depends on that.
I am aware of this difference, but there is something else to consider: Nowadays, many packages are not even installing static libraries any more. KDE3 packages, for example, traditionally don't install any static libraries (and if some package does it, they are removed very quickly). They are installing .la files (needed because of libltdl...), but they are not affected by the indirect dependency problem because they are using --as-needed. Other packages like libzypp and glib2 are not installing static libraries either, but their "consumers" inherit all private dependencies anyway because of the .la files. In the case of libzypp and glib2 (and all libraries built on top of glib2), the usefulness of their .la files is highly questionable because they cannot be used to create static executables anyway. With libzypp.la, but no libzypp.a this is just impossible. They could be used to create semi-static executables (where some libraries are linked static and others shared), but for this purpose, the .la files of pure shared libraries are not needed. Andreas Hanke -- "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
