From: Francesco Riosa <vivo75@gmail.com>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Proliferation of IUSE=static-libs in Gentoo
Date: Fri, 9 Mar 2018 00:12:25 +0100 [thread overview]
Message-ID: <CAD6zcDyFVNK=9mAn+1aD1doc9zuKHSOnk7n165fWC=60zZs8Jg@mail.gmail.com> (raw)
In-Reply-To: <1520523644.13614.14.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]
2018-03-08 16:40 GMT+01:00 Michał Górny <mgorny@gentoo.org>:
> Hello, developers.
>
> I would like to bring to your attention an alarming trend in Gentoo
> ebuilds -- the proliferation of IUSE=static-libs, that is a flag
> allowing our users to build static libraries.
>
> I should like to remind you that static linking is almost always a bad
> idea. It has serious security implications, it is poorly supported on
> *nix systems (example: library dependencies are provided via hacks, we
> don't have proper rebuild capabilities) and should be basically
> considered a great evil. Partially relevant doc: [1].
>
> This is why Gentoo does not generally support statically linking stuff,
> and we force dynamic linking whenever possible (sometimes even going too
> far with that but that's another story). We only allow static linking
> for special cases where shared linking can't be used for one reason
> or another.
>
> As part of that we also shouldn't deliver static libraries unless
> absolutely necessary to satisfy the dependencies of applications which
> we support built statically. Back in the day, Gentoo developers were
> pushing against packages that built static libraries unconditionally.
> However, it seems that at some point this front changed from 'fighting
> unconditionally built static libraries' to 'proliferating USE=static-
> libs everywhere'. Which is bad.
>
> So, developers, please *stop adding USE=static-libs* to random libraries
> that have no reason whatever to be statically linked to. And by that I
> mean a good reason, not creeping featurism, not 'user asked for it', not
> 'this broken package hardcodes libfoo.a'.
>
this would make impossible to use qemu static with binfmt alas
https://wiki.debian.org/QemuUserEmulation
Also looking for which packages are eligible for static libraries or not is
more work, not less, because it's a whole different layer of dependancies
(when doing the qemu stuff I just decided to build static for everything
rather than manage use flags per package)
[-- Attachment #2: Type: text/html, Size: 2581 bytes --]
next prev parent reply other threads:[~2018-03-08 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 15:40 [gentoo-dev] Proliferation of IUSE=static-libs in Gentoo Michał Górny
2018-03-08 15:59 ` Alec Warner
2018-03-08 16:13 ` Rich Freeman
2018-03-08 16:57 ` Jeroen Roovers
2018-03-12 13:53 ` Andrey Utkin
2018-03-12 14:06 ` James Le Cuirot
2018-03-08 20:16 ` James Le Cuirot
2018-03-08 23:12 ` Francesco Riosa [this message]
2018-03-10 11:01 ` Michael Orlitzky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD6zcDyFVNK=9mAn+1aD1doc9zuKHSOnk7n165fWC=60zZs8Jg@mail.gmail.com' \
--to=vivo75@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox