From: "François Bissey" <francois.bissey@canterbury.ac.nz>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] Clue transfer request: prefix/gx86 keywording policy/state-of-the-art?
Date: Mon, 02 Nov 2015 10:44:28 +1300 [thread overview]
Message-ID: <563687BC.80908@canterbury.ac.nz> (raw)
In-Reply-To: <CA+VB3NTtyqPh+VBC1H8SnC3npbnJsSQgs2FrL+6t8V6VZDRX3g@mail.gmail.com>
On 11/02/15 10:24, Greg Turner wrote:
> Consider this hypothetical KEYWORDS specifier I generated merging some
> gx86 and prefix content:
>
> KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc
> ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd ~sparc-fbsd ~x86-fbsd
> ~ppc-aix ~x64-freebsd ~x86-freebsd ~hppa-hpux ~ia64-hpux ~x86-interix
> ~amd64-linux ~ia64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos
> ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
>
> I don't see a lot of stuff like the above ... well, anywhere. So ...
> is it wrong? I'm at a loss as to why it would be.
>
> Perhaps, is it SOP to rely on prefixes accepting gx86 keywords from
> non-prefix arch'es they correspond to? Doesn't that tend to defeat
> the whole purpose of having prefix-specific keywords as we move toward
> a single-shared-tree future?
>
> tia for any insights!
>
> -gmt
>
While the need for it is fading fast for me I always would
have liked to have a ~ppc64-linux keyword. Going forward
would suit me in that regard at least for the linux platform.
For stuff like aix and other unixes in the prefix tree it may
or may not be a good idea on a platform by platform basis.
I can only judge for aix and macos.
Francois
next prev parent reply other threads:[~2015-11-01 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 21:24 [gentoo-alt] Clue transfer request: prefix/gx86 keywording policy/state-of-the-art? Greg Turner
2015-11-01 21:44 ` François Bissey [this message]
2015-11-02 9:39 ` Fabian Groffen
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=563687BC.80908@canterbury.ac.nz \
--to=francois.bissey@canterbury.ac.nz \
--cc=gentoo-alt@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