From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proliferation of IUSE=static-libs in Gentoo
Date: Sat, 10 Mar 2018 06:01:39 -0500 [thread overview]
Message-ID: <0a9db802-a0a5-e582-40a8-5da499eeb926@gentoo.org> (raw)
In-Reply-To: <1520523644.13614.14.camel@gentoo.org>
On 03/08/2018 10:40 AM, Michał Górny wrote:
>
> 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'.
>
> If upstream doesn't build static libraries by default, don't add flags
> to make it do it.
I've felt the same way for a long time. Flexibility is usually good, but
we shouldn't be going out of our way to add time bombs just because
"safe OR fragile" is technically added flexibility.
prev parent reply other threads:[~2018-03-10 11:01 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
2018-03-10 11:01 ` Michael Orlitzky [this message]
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=0a9db802-a0a5-e582-40a8-5da499eeb926@gentoo.org \
--to=mjo@gentoo.org \
--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