From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8CD8D1386F3 for ; Wed, 12 Aug 2015 16:53:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A094514293; Wed, 12 Aug 2015 16:53:10 +0000 (UTC) Received: from a1www.kph.uni-mainz.de (a1www.kph.uni-mainz.de [134.93.134.1]) (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 78DDC1427E for ; Wed, 12 Aug 2015 16:53:09 +0000 (UTC) Received: from a1i15.kph.uni-mainz.de (a1i15.kph.uni-mainz.de [134.93.134.92]) by a1www.kph.uni-mainz.de (8.14.9/8.14.7) with ESMTP id t7CGr7YA012927 for ; Wed, 12 Aug 2015 18:53:07 +0200 Received: from a1i15.kph.uni-mainz.de (localhost [127.0.0.1]) by a1i15.kph.uni-mainz.de (8.14.8/8.14.2) with ESMTP id t7CGr74D028789; Wed, 12 Aug 2015 18:53:07 +0200 Received: (from ulm@localhost) by a1i15.kph.uni-mainz.de (8.14.8/8.14.8/Submit) id t7CGr7wM028787; Wed, 12 Aug 2015 18:53:07 +0200 Message-ID: <21963.31219.307812.166298@a1i15.kph.uni-mainz.de> Date: Wed, 12 Aug 2015 18:53:07 +0200 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: useflag policies In-Reply-To: <55CB73E3.8000300@gentoo.org> References: <55C7AC24.2040503@gentoo.org> <55C9CA32.3060300@gentoo.org> <55C9F189.10102@gentoo.org> <20150812052120.5a83c3b1@googlemail.com> <20150812150349.00f8c8f9@gentoo.org> <21963.24971.636400.468846@a1i15.kph.uni-mainz.de> <55CB669F.8020501@gentoo.org> <20150812175547.3e889a82@gentoo.org> <55CB73E3.8000300@gentoo.org> X-Mailer: VM 8.2.0b under 24.3.1 (x86_64-pc-linux-gnu) From: Ulrich Mueller 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; boundary="pgp+signed+pxXhGSZhWVh6Bq2"; micalg=pgp-sha256; protocol="application/pgp-signature" X-Archives-Salt: 8182ce0d-f3f0-43c9-8f3b-97b7fb28a20e X-Archives-Hash: 1c25a6bae50834894adc07d87d3cec56 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --pgp+signed+pxXhGSZhWVh6Bq2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit >>>>> On Wed, 12 Aug 2015, Ian Stakenvicius wrote: > On 12/08/15 11:55 AM, Alexis Ballier wrote: >> I think it is better seen as a list of implications, esp. for >> this kind of questions :) With that in mind, there is no >> autounmask-write: effective USE for a given package is input USE >> with these implications applied. This very well summarises it. > ..if I'm understanding what you're saying here, you see this as > something the PM will use to adjust the input use list so that the > emerge itself will go ahead with the newly adjusted flags; am I > understanding that correctly? > In other words, there won't be any user control/alert/override for > what the default actions will be, if the user's profile isn't set up > in a way that satisfies REQUIRED_USE, correct? so if I have > 'app-cat/pkg qt4' in my package.use, but USE="qt5" in my profile, > then because both flags end up being enabled the REQUIRED_USE="^^ ( > +qt5 qt4 )" in app-cat/pkg will just force-off my package.use entry > and everything will proceed as if it wasn't there? Indeed, maybe there would be too much magic at work there. However, note that also currently you won't be able to emerge the package with a package.use that results in conflicting flags. Ulrich --pgp+signed+pxXhGSZhWVh6Bq2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCAAGBQJVy3nyAAoJEMMJBoUcYcJzeggIAIeQfSIbCbwB8txMzjLVwkK8 XYKq7R2TnLWnWpSVJ9NlR5ZMHcgf2KnzJYNjk6csDzkNW+2HR3eqQvXxrHkJIeEY yTYBIljnuX32LABIb9tM3fUn3r0ylimEFzAmZqMOJZbvChqCOd/Qw8trZSfiK3dq zARWtW1Qi4UmJqql56QotDP70mX0taH2FM5vRuzd6SS3+mYonG3HZ7vrdfYfNnAp j6NdE2USfh4SSbJlNrIerYs+PiatDD+kt8iN2Hnd8NdifXs8a/3Xc/GjPFdGTjJX WBrmU1R19hwLInEmh1eOf63nhkR0eqjUo0SJ3dUKN+GF+nzSzBc9o3S7NX4vIeo= =++4b -----END PGP SIGNATURE----- --pgp+signed+pxXhGSZhWVh6Bq2--