Description of problem: There is a static library in libesmtp. I think it should be either dropped or put in libesmtp-static. In the case of libesmtp, I am in favor of dropping it, since dlsym is used, the ABI is stable and security issues are relevant for libesmtp. I can do a patch once a solution is agreed. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I see this library is a part of libesmtp-devel package. This is similar to many other libraries (openssl, libxslt, to name two of them). Is there any reason to deviate from this apparent convention?
It is in the guidelines since a few months. Also, in general, the packages from core that haven't finished their merge review are in bad state with respect with guidelines. I don't know about those packages, but in any case static libs should be in -static subpackages or not shipped. http://fedoraproject.org/wiki/Packaging/Guidelines#head-2302ec1e1f44202c9cc4bcce24cb711266557ad7 You can see that I am not an opponent of static libs: http://fedoraproject.org/wiki/PatriceDumas
Patch commited - thank you!
An alternative way to avoid the static library, including avoiding to build it in the first place is to pass to %configure: --disable-static
also %{_libdir}/libesmtp.a is still listed
Can I implement myself the fixes I propose?
Go ahead - I am currently out, travelling.