On Sat, 4 Apr 2020 08:12:09 +0200 Alessandro Barbieri <[email protected]> wrote:
> I was trying to remove static-libs from hwloc and I noticed that the last > bump of ceph is requiring hwloc:=[static-libs?] > And I notices it needs also alot of other dependencies with [static-libs?] > Is there a *valid* reason for having ceph[static-libs] around in the first > place? > > For more context on static-libs see: > https://projects.gentoo.org/qa/policy-guide/installed-files.html?highlight=static#pg0302 > https://flameeyes.blog/2011/08/29/useless-flag-static-libs/ > https://archives.gentoo.org/gentoo-dev/message/2dada80c2b9c85b0e83e6328428bf8ab I do like to have the option for static-libs where it's not too much trouble. It's obviously not a mainline use case but I have needed it on occasions. I think these dependencies are wrong though and I've seen the same thing in other packages. You don't need the dependent static libs when building other static libs. For example. I have webp[-static-libs] installed and I can build leptonica[static-libs,webp] just fine. They are only needed when linking executable binaries and for that, you'll typically have a static USE flag rather than static-libs. QEMU is a good example with its static and static-user USE flags. You could force a package to build static or partially static binaries through toolchain flags but then it's down to the user to ensure that all the dependent static libs are in place. If the above paragraph is wrong, someone please correct me. :) -- James Le Cuirot (chewi) Gentoo Linux Developer
pgpzFwxdMGt1r.pgp
Description: OpenPGP digital signature
