https://bugzilla.redhat.com/show_bug.cgi?id=970956
--- Comment #4 from Björn Esser <bjoern.es...@gmail.com> --- (In reply to Michael Schwendt from comment #3) > There's a hint in comment 1: > > | There's only a static lib generated during %build, > | which isn't packaged at all. > > You cannot simply delete the compiled/built library in %install. You need to > package it in accordance with > https://fedoraproject.org/wiki/Packaging: > Guidelines#Packaging_Static_Libraries The other way would be patching Makefile(.am) to build a shlib instead, regenerate with `autoreconf -vfi` (if applicable) and package it that way. Just having headers is usually (best known exception is boost-base, but it's specially designed this way) not enough in C/C++. There need to be binary-libs to link against. Just packaging the static lib is not such a good approach, since on main goal in development of Fedora is to get rid of them. The other problem I see is, if someone ports a daemon-app from bsd to Fedora using libclens-static, usefully hardening this is close to impossible. Linking against static libs doesn't allow PIE and RELRO with immeditate binding. The next question comming into my mind: What does libclens provide additionally to libbsd? Is it really worth the affort? -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=BwNETTfeY0&a=cc_unsubscribe _______________________________________________ package-review mailing list package-review@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/package-review