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 87973139694 for ; Mon, 29 May 2017 16:31:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0BAADE0E36; Mon, 29 May 2017 16:31:00 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BCFFEE0E06 for ; Mon, 29 May 2017 16:30:59 +0000 (UTC) Received: from katipo2.lan (unknown [203.86.205.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kentnl) by smtp.gentoo.org (Postfix) with ESMTPSA id 0247C3416E8 for ; Mon, 29 May 2017 16:30:57 +0000 (UTC) Date: Tue, 30 May 2017 04:30:27 +1200 From: Kent Fredric To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] Forced/automatic USE flag constraints (codename: ENFORCED_USE) Message-ID: <20170530043027.5e5b8615@katipo2.lan> In-Reply-To: <1496071993.31087.1.camel@gentoo.org> References: <1496071993.31087.1.camel@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) 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 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/DMJ9LoSbGTgT0nx6pwJF.E4"; protocol="application/pgp-signature" X-Archives-Salt: 8c08269a-5ec4-48ed-8fee-78df5b6122c0 X-Archives-Hash: 30714764bad3b24b5f6fce7eb4748dab --Sig_/DMJ9LoSbGTgT0nx6pwJF.E4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 29 May 2017 17:33:13 +0200 Micha=C5=82 G=C3=B3rny wrote: > Automatically solving USE constraints solve all three fore-mentioned > issues with REQUIRED_USE. By default, no user intervention is required > to solve USE constraints and package.use needs to be modified only to > enforce a non-standard solutons Overall I like the proposal, but one question: How do you envisage automatic use-constraints interacting with --newuse? I have this feeling that "automatically enabled" flags could somehow have an ephemeral nature, where a flag would be enabled at build time, and then later a subsequent change in the graph toggles the flag off, creating a potentially undesirable rebuild. I feel I might be imagining a problem because I might have a wire crossed somewhere, so some sort of confirmation that I'm the insane one and this can't happen would be reassuring :)=20 --Sig_/DMJ9LoSbGTgT0nx6pwJF.E4 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPZazbI/qrFT1o9rn6FQySxNmqCAFAlksTK8ACgkQ6FQySxNm qCA6EA//blpdIQq1jdmoI8tn/K6Vn37jCvVvIsiDylSQxyyPoARUjzNdoIVCTAqu FEvEErvw0xmxty/Gx0rc+RwSyGqdYvTnT5TXTcTBDNZEGCuI+l1g7otIRhJNHm/Z n20mRAi5Z6qC4YbHcRYmesqesFWUU8YcJKLzpjJHy8lAf7O/QV4PsVlFm88BKezj sQiK0H0JOqy19TrEpCxN5/1jklGtTXfpEnpdXDcrKjRRLD37Gy774BZOsDyBWsfL 2k0P6qGWXL0O9turGlLiPHBsuAgWYA0G+56b87jm9d2GXRweCllABnW4e6oM2w0y HnuH+HDE2+TrMyJ78q9WyoIdDkWeAiV9LLvQPsyEgBTla6FhZ6gk5okIzEldUJQY NVa/k97aEvGbDqLIAr5z8g1RriqGpgrXl4U20H2s3EumZVFCLCd80CDfuv7FhwlH 0D0vcpEGO0NGzryWPHAThn+/Rk+gg0IsrrCxU3ppfMtvuwOh1vTvnLz6r8ReiHEa P2B3F0McOBa2NJbgRB46WbNd32/YEl2geKh2ZPuccdkNrKrjghhAipjPt7WYdYmW n6MhHnFMtHFieAj2vvaN5xocLJdqtovPgfpFY6gVxw0kJqNqnok3BiVzXRRqNKps XXQyaTPNl7qhS+wok0/wz64QM3JP3Ifif1KVGuJVB+2Zdkhy0MY= =TDYg -----END PGP SIGNATURE----- --Sig_/DMJ9LoSbGTgT0nx6pwJF.E4--