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 9C22C1381F4 for ; Wed, 15 Aug 2012 15:02:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 04A25E0952 for ; Wed, 15 Aug 2012 15:02:53 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 3EF5021C065 for ; Wed, 15 Aug 2012 12:22:55 +0000 (UTC) Received: from pomiocik.lan (87-205-57-138.adsl.inetia.pl [87.205.57.138]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 7D73F1B400F; Wed, 15 Aug 2012 12:22:53 +0000 (UTC) Date: Wed, 15 Aug 2012 14:23:40 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-project@lists.gentoo.org Cc: ciaran.mccreesh@googlemail.com Subject: Re: [gentoo-project] Council meeting: Tuesday 14 August 2012, 19:00 UTC Message-ID: <20120815142340.2a7d6ff8@pomiocik.lan> In-Reply-To: <20120815131217.24c506d4@googlemail.com> References: <20120807191736.GF49719@gentoo.org> <20520.6784.427242.325755@a1i15.kph.uni-mainz.de> <20522.23125.717981.676275@a1i15.kph.uni-mainz.de> <201208142318.01431.dilfridge@gentoo.org> <20120814223556.780b481d@googlemail.com> <502AC963.5040000@gentoo.org> <20120814230204.1eada549@googlemail.com> <20120815002021.0676b290@pomiocik.lan> <20120815130131.1a3f10a8@googlemail.com> <20120815141155.595e86ea@pomiocik.lan> <20120815131217.24c506d4@googlemail.com> Organization: Gentoo X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.11; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/e2kkL.f4qW/PEEzwgA0PvDd"; protocol="application/pgp-signature" X-Archives-Salt: 5cbbe3fa-fc27-460a-a53e-97d32f5321c0 X-Archives-Hash: 69ef46a507914507bd1421e7946d92bf --Sig_/e2kkL.f4qW/PEEzwgA0PvDd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, 15 Aug 2012 13:12:17 +0100 Ciaran McCreesh wrote: > On Wed, 15 Aug 2012 14:11:55 +0200 > Micha=C5=82 G=C3=B3rny wrote: > > > Whichever route we go, there's also the UI question: how do we > > > present this to users in a sensible way? > >=20 > > The intent is not to anything clever but just mask the package. > > Intel users don't want mesa without support for their card; they > > simply don't want the broken version at all. > >=20 > > It should be presented alike regular package.mask, with the whole > > atom string. >=20 > I'm not sure that it's that simple: what if a user has, say, intel > turned on only because it's on by default in profiles? In this particular case -- nothing, because he has by default other card settings which make mesa don't trigger the bug. It was simply a very weird bug which needed a simple solution to avoid spreading it on users. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/e2kkL.f4qW/PEEzwgA0PvDd Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAlArlMwACgkQfXuS5UK5QB3xyQP+J++3mfXNqA1NqTSFGmYrc6GT jgqFwCRz8mCl6IbHEAQSImQFX1VlFO0DJG4mlTqzF4WJ9t/VwJFKExMr8qSvvon1 UrlDs4pHmJOU5qT9BzFGbLATfNOxfz84UGWH+eRXkUNTR0gqWccwwJNJewhv+FZn tvxB54eJ1ZJgOaInJrs= =Xj7G -----END PGP SIGNATURE----- --Sig_/e2kkL.f4qW/PEEzwgA0PvDd--