From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: cartesian product extension to keyword system
Date: Mon, 29 Apr 2013 15:43:03 +0200 [thread overview]
Message-ID: <20130429154303.52b66c5b@marga.jer-c2.orkz.net> (raw)
In-Reply-To: <87ppxdajv8.fsf@proton.in.awa.tohoku.ac.jp>
On Mon, 29 Apr 2013 16:14:51 +0900
heroxbd <heroxbd@gentoo.org> wrote:
> KEYWORDS="~hppa-hpux ~m68k-mint ~ppc-aix ~x64-solaris ~x86-interix["]
>
> KEYWORDS_ARCH="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64
> ~s390 ~sh ~sparc ~x86"
Regardless of your chance of success in making the extra complexity
manageable, I think moving the tradition KEYWORDS value to
KEYWORDS_ARCH, and reusing KEYWORDS for something else , would
needlessly increase the work required to "migrate" the portage tree.
Why not leave KEYWORDS what it is right now, and expand/change its
meaning using alternate variables so that you can (indefinitely)
maintain backward compatibility?
jer
next prev parent reply other threads:[~2013-04-29 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 7:14 [gentoo-dev] RFC: cartesian product extension to keyword system heroxbd
2013-04-29 7:39 ` Fabian Groffen
2013-04-29 9:26 ` heroxbd
2013-04-29 7:53 ` Ben de Groot
2013-04-29 9:31 ` heroxbd
2013-04-29 13:43 ` Jeroen Roovers [this message]
2013-05-09 13:38 ` Alexey Shvetsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130429154303.52b66c5b@marga.jer-c2.orkz.net \
--to=jer@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox