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: [gentoo-dev] [RFC] New keywords for non-Gentoo Linux platforms
Date: Thu, 9 Oct 2008 20:11:01 +0200	[thread overview]
Message-ID: <20081009181101.GE21770@gentoo.org> (raw)

Hi all,

In the Prefix project we support a bunch of Linux and non-Linux
platforms, for which we use GLEP53-style[1] keywords.  The current list
of keywords known in Prefix are (in no particular order):

	ppc-aix
	x86-freebsd
	ia64-hpux
	hppa-hpux
	x86-interix
	mips-irix
	amd64-linux
	x86-linux
	ppc-macos
	x86-macos
	x86-netbsd
	ppc-openbsd
	x86-openbsd
	x64-openbsd
	sparc-solaris
	sparc64-solaris
	x64-solaris
	x86-solaris
	x86-winnt

Most notably, in Prefix all keywords are full GLEP53 style, which
results in e.g. amd64-linux.  We did this on purpose, because in Prefix
we don't necessarily are on Gentoo Linux.  We also chose to expand fbsd,
nbsd and obsd to their long variants, mainly because the short variants
might clash in the future, for e.g. OpenBSD, OliveBSD or PicoBSD,
polyBSD or DragonflyBSD, DesktopBSD.  (At some point we were a bit
over-enthausiastic.)

I would like to hear some opinions on the keywords in general, as well
as the particular problem of having Gentoo Linux, and a Linux supported
by Gentoo Prefix.  Right now there is just the difference of "-linux"
appended, however this is not the clearest distinction between the two.
Perhaps using KEYWORDS for Prefix keywords is not the best thing to do,
and should we use something like PREFIX_KEYWORDS?


[1] http://www.gentoo.org/proj/en/glep/glep-0053.html

-- 
Fabian Groffen
Gentoo on a different level



             reply	other threads:[~2008-10-09 18:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 18:11 Fabian Groffen [this message]
2008-10-09 22:05 ` [gentoo-dev] [RFC] New keywords for non-Gentoo Linux platforms Marius Mauch
2008-10-10  0:16   ` [gentoo-dev] " Duncan
2008-10-10  2:21     ` Marius Mauch
2008-10-10  7:15       ` Fabian Groffen
2008-10-10 12:40         ` Diego 'Flameeyes' Pettenò
2008-10-10 12:48           ` Fabian Groffen
2008-10-10 15:56             ` Marius Mauch
2008-10-10 16:13               ` Robert Bridge
2008-10-10 15:21         ` Ryan Hill
2008-10-10  8:56 ` [gentoo-dev] " Michael Haubenwallner
2008-10-10 12:56 ` Jeremy Olexa
2008-10-13  5:16   ` [gentoo-dev] " Steve Long
2008-10-13 14:27     ` Ciaran McCreesh
2008-10-13 17:59       ` Fabian Groffen
2008-10-14  7:48         ` Michael Haubenwallner
2008-10-15 10:20           ` [gentoo-dev] " Steve Long
2008-10-17 14:22 ` [gentoo-dev] " Michael Haubenwallner
2008-10-21 14:09   ` [gentoo-dev] " Tiziano Müller
2008-10-21 19:01     ` 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=20081009181101.GE21770@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