The package is in need of an update because it does not adhere to the guidelines for packaging static libraries: http://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_Static_Libraries The -devel package contains both the shared and the static build of a library. That makes it possible to link statically with the -devel package as a build requirement instead of having to build-require a special-purpose -static subpackage. Correct would be to either disable/delete the static libraries at build-time, or to %exclude them in the %files section, or to split off a -static subpackage (if there is a compelling reason as why the static libs should be made available). Please consult the guidelines for the details. [...] libxslt-devel /usr/lib/libexslt.so <=> /usr/lib/libexslt.a /usr/lib/libxslt.so <=> /usr/lib/libxslt.a
From the 61 src.rpms in Rawhide, which want libxslt-devel, only two mention "-static" or the static libraries in the build log: q : it links shared in the final compiler invocation wine : the -static linkage is unrelated to libxslt Several packages don't mention xsltproc or -lxslt/-lexslt in the build log: bmpanel2: bug 572633 compiz-bcop : checks for libxslt, but doesn't use it anywhere kdebase3 : ? kdepim : kdepim-runtime build is linked shared kvkbd : checks for libxslt, but build.log is non-verbose cmake libgnome : ? netcf : build is linked shared oyranos : ? qt : ? webkitgtk : build is linked shared Those above with '?' might either not produce verbose build log output, or not need libxslt-devel, or only add it to make a build framework happy.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fixed in rawhide: libxslt-1.1.26-2.fc14 I dropped the static libs entirely, after confirming that q builds properly against the shared library when the static library is not present. (I rebuilt q as well in rawhide).