public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: cartesian product extension to keyword system
Date: Mon, 29 Apr 2013 09:39:08 +0200	[thread overview]
Message-ID: <20130429073908.GR96262@gentoo.org> (raw)
In-Reply-To: <87ppxdajv8.fsf@proton.in.awa.tohoku.ac.jp>

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

Hi,

On 29-04-2013 16:14:51 +0900, heroxbd wrote:
> In GLEP22[1], reasonable defaults has been introduced to prevent the
> explosion of keywords. With the growth of Gentoo Prefix, however, a
> substantial amount of keywords are introduced. Among them, duplex
> information exists. For example, an ebuild keyworded x86-linux(Gentoo
> Prefix on x86 linux) will certainly build on x86 (Gentoo vanilla on x86
> linux).

Likely, but not necessary true.

> Furthermore if the ebuild has "amd64" keyword, it will certainly
> build on amd64-linux too.

Somewhat likely, but absolutely not true.

> Therefore we propose the following cartesian product extension to
> keyword system.

We added the keywords as is, to uniquely define which systems it works
on.  Assuming something will work because it should be similar is (and
has been proven in the past to be) wrong.

My €0.02

-- 
Fabian Groffen
Gentoo on a different level

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2013-04-29  7:39 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 [this message]
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
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=20130429073908.GR96262@gentoo.org \
    --to=grobian@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