From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 738CB1382C5 for ; Sat, 10 Mar 2018 11:01:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B8AADE087B; Sat, 10 Mar 2018 11:01:51 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 63F61E083B for ; Sat, 10 Mar 2018 11:01:51 +0000 (UTC) Received: from [192.168.1.100] (c-98-218-46-55.hsd1.md.comcast.net [98.218.46.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id F0690335C2A for ; Sat, 10 Mar 2018 11:01:49 +0000 (UTC) Subject: Re: [gentoo-dev] Proliferation of IUSE=static-libs in Gentoo To: gentoo-dev@lists.gentoo.org References: <1520523644.13614.14.camel@gentoo.org> From: Michael Orlitzky Message-ID: <0a9db802-a0a5-e582-40a8-5da499eeb926@gentoo.org> Date: Sat, 10 Mar 2018 06:01:39 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <1520523644.13614.14.camel@gentoo.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Archives-Salt: 70c4dde9-ea98-471d-849e-92b6a296f5db X-Archives-Hash: 1c2f48a7d4fe77a88a1569884c496813 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.