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