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 470B2138247 for ; Fri, 17 Jan 2014 15:02:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4F431E0ADA; Fri, 17 Jan 2014 15:02:41 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 419BAE0AD8 for ; Fri, 17 Jan 2014 15:02:40 +0000 (UTC) Received: from pomiot.lan (static-81-219-166-219.devs.futuro.pl [81.219.166.219]) (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 40E1F33F8F2; Fri, 17 Jan 2014 15:02:38 +0000 (UTC) Date: Fri, 17 Jan 2014 16:02:27 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Cc: grozin@gentoo.org Subject: Re: [gentoo-dev] rfc: revisiting our stabilization policy Message-ID: <20140117160227.7853d878@pomiot.lan> In-Reply-To: References: <20140114213719.GA2684@laptop.home> <52D6715F.8000502@gentoo.org> <20140115153036.GA1433@laptop.home> <52D77990.7060506@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; 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-sha512; boundary="Sig_/1UedPrpCUzQqOqxO0fgY=cv"; protocol="application/pgp-signature" X-Archives-Salt: a3531ed6-f983-44e7-9303-23283dd3e66d X-Archives-Hash: b997b70e2fb835c3ce5ca1d716f832ac --Sig_/1UedPrpCUzQqOqxO0fgY=cv Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dnia 2014-01-17, o godz. 14:02:51 grozin@gentoo.org napisa=C5=82(a): > Maybe, a good solution is to introduce a special arch, "noarch", for such= =20 > packages (similar to what's done in the rpm world). Then, if a package is= =20 > ~noarch, it is automatically considered ~arch for all arches. Similar for= =20 > stable. The maintainer should be able to keyword ~noarch and to stabilize= =20 > noarch. Comments? If you want to play with such a major change, you should start a new thread instead of starting it in the middle of this spam-art. Otherwise, many people will miss it and complain loudly afterwards. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/1UedPrpCUzQqOqxO0fgY=cv Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQJ8BAEBCgBmBQJS2UYGXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOc0sP/0B1pQfD5g6vh1u+Kd5G0gbb J1CmTID+aYdbTqc0vSc/6v2wu//hQspRpIoIRbB7YebCHpOZodgeSyMYZwT3IIrd YdBWbMYaRmEm4fOwc4+W/gMg/qs75ceoXyvKdnmWpLFqEpbYILJiAfDz7yHK+D5c gQfS4EOilzvfGBxFkmAgh/MugFSlTxzCQJt0lYmRjco54EWEnEYkctFQ227OpscG 1g3CGt4A2lu0bawkORcNi6ser2xQqAp/AwNFSGgUMQK/5W3QFY7LyHYkkB9Z+WDn 9SAqEnIainRQMkQtxym2eUsapqWi9Do+ysTIbfbNpDwG27WlgiHULFF2CB9/v1+s 0Svs+HAPIPhfOmZgRP73z4kdYEdfLXTmInea06If4HBQ9XrBFfHDL7niNW46EJ+V IGSJyRrHhq1Uv2N2sjZCjTQ1trjc1i16HWkCAhVDjimFUGSu4SwBaEWoqY1DnMsQ ub+DtSqnhixApcl/zAt8xc4Ue2Hh3ZfDWOAAj8YHOcF/oxXVPyK0nP3saEoVgAqZ DhYRTWZ5KfISDn5se6HvJluW0wqyOkdhiostLnTP5Es2Kz4WbNjo9Aswdk3kOfnQ U//henz6me24JByBm2scjQAVM2lG5VvBJ77UbedrsTYYmTxGLnJYK7BsU+Knlut5 Y/nmjabnZCaVjAM1TArq =Polk -----END PGP SIGNATURE----- --Sig_/1UedPrpCUzQqOqxO0fgY=cv--