Re: [gentoo-dev] [RFC] New keywords for non-Gentoo Linux platforms

2008-10-17 Thread Michael Haubenwallner

On Thu, 2008-10-09 at 20:11 +0200, Fabian Groffen wrote:

   sparc-solaris
   sparc64-solaris
   x64-solaris
   x86-solaris

 Perhaps using KEYWORDS for Prefix keywords is not the best thing to do,
 and should we use something like PREFIX_KEYWORDS?

Maybe there is one thing we should consider:
Since the Solaris kernel is Open now (=OpenSolaris), one could have the
strange idea of adding some sys-kernel/solaris-sources-2.11.ebuild, to
build some distribution eventually called Gentoo Solaris, which might
be comparable to Nexenta[1], which uses Debian's APT AFAICS.

As Gentoo Solaris would not be the same as Gentoo Prefix on Solaris,
it should not share the *-solaris keywords used for Prefix via the same
KEYWORDS-setting.

For me, this is a (maybe strange, but valid) reason for something like
PREFIX_KEYWORDS.

[1] http://www.nexenta.org/

/haubi/
-- 
Michael Haubenwallner
Gentoo on a different level




Re: [gentoo-dev] [RFC] New keywords for non-Gentoo Linux platforms

2008-10-10 Thread Jeremy Olexa

Fabian Groffen wrote:
snip

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?



Ignoring the bit about how to name the keywords.. ;)

I am undecided about Prefix keywords in the normal KEYWORDS variable. In 
particular, we are overloading the -linux keyword to mean that it will 
run on any linux that Gentoo Prefix supports. This includes, Gentoo, 
RHEL, SLES, FreeMint, $OTHER.


Is there any problem with overloading the keywords like that? If not, 
then it shouldn't be a problem to keep prefix keywords in the KEYWORDS 
field. OTOH, I don't think we should add another variable to ebuilds.


Thoughts?

-Jeremy




Re: [gentoo-dev] [RFC] New keywords for non-Gentoo Linux platforms

2008-10-10 Thread Michael Haubenwallner

On Thu, 2008-10-09 at 20:11 +0200, Fabian Groffen wrote:

   ia64-hpux

There's one thing to say for this platform to avoid later confusion:

'ia64-hpux' is the keyword for 32bit on that platform.
'ia64w-hpux' would be the 64bit keyword (not in prefix-tree yet).

This might seem confusing, but is the way HP does for various reasons.

HP-UX is the only OS I know that does multilib on the ia64 CPU, and the
default compiler output is 32bit without any additional switch.

I can provide more details if necessary.

/haubi/
-- 
Michael Haubenwallner
Gentoo on a different level




Re: [gentoo-dev] [RFC] New keywords for non-Gentoo Linux platforms

2008-10-09 Thread Marius Mauch
On Thu, 9 Oct 2008 20:11:01 +0200
Fabian Groffen [EMAIL PROTECTED] wrote:

   amd64-linux
   x64-openbsd
   x64-solaris

Is there a special reason why you're using x64 instead of amd64 in
those cases? (IMO x64 is the most stupid name for the x86_64
architecture)

Marius