From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1ON0WX-0000mv-7T for garchives@archives.gentoo.org; Fri, 11 Jun 2010 09:27:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 508C9E0B87; Fri, 11 Jun 2010 09:27:35 +0000 (UTC) Received: from smtp01.jazztel.es (smtp01.jazztel.es [62.14.3.170]) by pigeon.gentoo.org (Postfix) with ESMTP id 45C6DE0B57 for ; Fri, 11 Jun 2010 09:27:30 +0000 (UTC) Received: from [87.222.150.205] (helo=[192.168.1.201]) by smtp01.jazztel.es with esmtpa (Exim 4.69) (envelope-from ) id 1ON0WP-0001CO-CH for gentoo-dev@lists.gentoo.org; Fri, 11 Jun 2010 11:27:29 +0200 Subject: [gentoo-dev] Suggestion related with dropping keywords policy From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-XjFDjOYhgwYDhpopRvPu" Date: Fri, 11 Jun 2010 11:27:22 +0200 Message-ID: <1276248442.17113.16.camel@localhost.localdomain> 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 X-Mailer: Evolution 2.28.3.1 X-AntiSpam-Checked: Passed : Threshold - 0.0 : SA jazztel.es X-Virus-Checked: Passed : Kaspersky at jazztel.es X-Archives-Salt: dcae8823-f247-44cd-a18e-45234b55ec90 X-Archives-Hash: 83ab693070bd7a5c3e1ff7261ac2be0c --=-XjFDjOYhgwYDhpopRvPu Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Let my explain the problem and my suggestion to handle it better (at least from my point of view) with an example: Sometime ago I bumped bluez version from 4.39-r2 to 4.60, with that bump, a new and *optional* RDEPEND on sys-libs/libcap-ng was added. Since libcap-ng was not keyworded in all arches but x86 and amd64, I had to drop keywords for bluez and open http://bugs.gentoo.org/show_bug.cgi?id=3D303527 for handling it. =46rom my point of view, I would prefer to: 1. Mask "caps" for net-wireless/bluez on affected arches, letting us to keep bluez keyworded. 2. Open two bug reports as done with current policy: one for keywording libcap-ng and other to check bluez works ok with it asking arch team to unmask that USE flag if possible. This way to go would have the advantage of letting people running bluez on affected arches to still get the latest bluez version instead of still having to run a pretty old (and buggy) one. Thanks for considering it --=-XjFDjOYhgwYDhpopRvPu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAkwSAXoACgkQCaWpQKGI+9TA+ACeI49/kyEZOtr6nBDrgzBoCgLr kGsAnRDCdOeHypW9ZA9xG51pTK+sy8J7 =rnIn -----END PGP SIGNATURE----- --=-XjFDjOYhgwYDhpopRvPu--