The static linking guidelines state that programs that link statically when a shared library exists need to have an exception from FESCo. Once the situation with binutils-static is resolved, I think it would make sense to apply a blanket exception for binutils-static as upstream is treating this as the static-library equivalent of a copylib. ie: you aren't supposed to bundle, but you are supposed to link statically since the public ABI changes with every release. Only the binutils tools themselves are supposed to use the dynamic libraries.
Text of the exception would be:
Any program may link against binutils-static without asking for a separate exception from FESCo as the binutils upstream only supports external libraries linking to the static libraries.
To be added to this section: https://fedoraproject.org/wiki/Packaging:Guidelines#Staticly_Linking_Executables
Filing this here for both FPC informational purposes and so that we collectively remember to take it to FESCo once https://bugzilla.redhat.com/show_bug.cgi?id=576300 is resolved.
Actually, looking at what's in git instead of what's in the bugzilla ticket, this appears to be fixed by going the route of "Static libraries only. When a package only provides static libraries you can place all the static library files in the -devel subpackage. When doing this you also must have a virtual Provide for the -static package: "
Closing
Login to comment on this ticket.