From: heroxbd <heroxbd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: cartesian product extension to keyword system
Date: Mon, 29 Apr 2013 18:26:18 +0900 [thread overview]
Message-ID: <87k3nlads5.fsf@proton.in.awa.tohoku.ac.jp> (raw)
In-Reply-To: <20130429073908.GR96262@gentoo.org> (Fabian Groffen's message of "Mon, 29 Apr 2013 09:39:08 +0200")
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
Dearr Fabian,
Fabian Groffen <grobian@gentoo.org> writes:
>> Furthermore if the ebuild has "amd64" keyword, it will certainly
>> build on amd64-linux too.
>
> Somewhat likely, but absolutely not true.
Sorry, the original phrase was vague. I meant, if an ebuild is keyworded
"amd64" and "x86-linux", it will certainly work on "amd64-linux"
>> 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.
Every system is different. We are grouping similar systems into
corresponding keywords, and already assuming ability for
extrapolation. And now we observe that ARCH and KERNEL are quite
independent. They can be decomposed into two dimensions. Why don't me
exploit this fact?
Cheers,
Benda
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-04-29 9:26 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 [this message]
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=87k3nlads5.fsf@proton.in.awa.tohoku.ac.jp \
--to=heroxbd@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