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 04B71138247 for ; Fri, 17 Jan 2014 07:58:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 36715E0B4D; Fri, 17 Jan 2014 07:58:26 +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 407C5E0B43 for ; Fri, 17 Jan 2014 07:58:25 +0000 (UTC) Received: from mail-qe0-f43.google.com (mail-qe0-f43.google.com [209.85.128.43]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mattst88) by smtp.gentoo.org (Postfix) with ESMTPSA id 6722533F874 for ; Fri, 17 Jan 2014 07:58:24 +0000 (UTC) Received: by mail-qe0-f43.google.com with SMTP id nc12so3607289qeb.16 for ; Thu, 16 Jan 2014 23:58:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=5yCRaKADAFhLj6A24dOE35i7pgpjqJcbWcfW8nXZ+2Q=; b=EXHnKZ2Ox2pP7C5zJpFE48SwcZ68yzm56zk4m5V0H84AAmvhnlrhBSziN+RaXrlb68 3NNaKAkP7jB3CWq6zEyMHIpD6Uk448IiBbKIziWSN6Bar6ufibOqb/+e3KooTRCv2wBZ ZiFk0YuoryZSWMvp3VRy+5Yg/g1yxcdpYhjVn+Hb0OD8cfTUvUNKsb4LSG4wC8IT5RaP /+7pWRtLUFIn9954jgRIB+C1NlfdjQNEQgH0+lN9DXq2OTZYYG/uHP/SkiWOC6TTRI25 bvEfLV4wdiygG1uAEov01uYFuaLO61CJPi84Bzxs5vb+N/uSooE0XN0yfwYAz8aW6Ops pwnQ== X-Received: by 10.224.41.10 with SMTP id m10mr843065qae.34.1389945502530; Thu, 16 Jan 2014 23:58:22 -0800 (PST) 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 Received: by 10.229.178.129 with HTTP; Thu, 16 Jan 2014 23:58:02 -0800 (PST) In-Reply-To: References: <20140114213719.GA2684@laptop.home> <52D6715F.8000502@gentoo.org> <20140115153036.GA1433@laptop.home> <52D77990.7060506@gentoo.org> From: Matt Turner Date: Thu, 16 Jan 2014 23:58:02 -0800 Message-ID: Subject: Re: [gentoo-dev] rfc: revisiting our stabilization policy To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: b5c4f769-e273-48be-a0a5-10ec0e71fba3 X-Archives-Hash: dcb40ad6853a0aab62fc62b257180998 On Thu, Jan 16, 2014 at 11:02 PM, wrote: > Sorry for following up myself, > > > On Fri, 17 Jan 2014, grozin@gentoo.org wrote: >> >> OK, let's be conservative. Python and Perl scripts may break on some >> arches (I'd say it's a rare exception, perhaps 1%, but still). But what >> about >> >> dev-java/java-sdk-docs >> dev-db/postgresql-docs >> sys-kernel/linux-docs >> dev-dotnet/gtk-sharp-docs >> app-xemacs/general-docs >> dev-util/kdevelop-php-docs >> dev-util/gnome-devel-docs >> app-vim/phpdocs >> gnome-extra/gnome-user-docs >> gnome-extra/gnome-getting-started-docs >> dev-php/smarty-docs >> dev-python/python-docs >> dev-python/cheetah-docs >> app-doc/php-docs >> app-doc/root-docs >> app-doc/geant-docs >> app-doc/blas-docs >> app-doc/lapack-docs >> app-doc/gnucash-docs >> app-office/abiword-docs >> dev-lisp/hyperspec >> sys-apps/man-pages[-*] >> >> and maybe others? They contain no scripts which can possibly break. I'd >> say they should be keyworded on all arches as soon as they are keyworded on >> the first arch; the same goes for stabilization. I'd include also packages >> containing only TeX/LaTeX code - TeX behaves identically on all arches, this >> was and is its main strength. Also, probably, python/perl/ruby interpreted >> scripts *which don't load extra libraries* work identically on all arches >> not in 99% of cases but in 99.99% (0.01% is for cases when the interpreter >> is broken on a given arch). > > Maybe, a good solution is to introduce a special arch, "noarch", for such > packages (similar to what's done in the rpm world). Then, if a package is > ~noarch, it is automatically considered ~arch for all arches. Similar for > stable. The maintainer should be able to keyword ~noarch and to stabilize > noarch. Comments? > > Andrey There's been opposition to this in the past, but I'm in favor of giving this a shot.