Re: [gentoo-dev] x86-fbsd keyword in main tree?

[Alec Warner]

Stephen Bennett wrote:
> On Thu, 09 Mar 2006 10:20:33 -0500
> Alec Warner <antarus@g.o> wrote:
>
>
>>Basically portage expands $ARCH into use ( so
>>x86-fbsd has ARCH x86, and would get "x86" in use, which IMHO, isn't
>>that horrible ). However, you also don't get x86-fbsd shoved into
>>USE, so you have to inject it elsewhere, and then users could do
>>something stupid like -x86-fbsd in make.conf, and unset their ARCH
>>flag = bad.
>
>
> The profiles currently in the overlay set ARCH=x86-fbsd. Whether that's
> right or not is another debate, but it invalidates that particular
> problem.

The problem being that your ARCH (architecture) IS x86, just as 
ppc-macos's architecture is ppc, and there may be patches that apply to 
both sets equally, and conversely things that apply to only linux.

Now if GLEP47 is approved, then the point is moot ( x86 implies 
x86-linux, or whatever the corresponding keyword is ).

If this is the tract we are going to head in I need to change the docs 
to reflect what ARCH really means.

At present in man portage:
ARCH   Architecture type (x86/ppc/hppa/etc...).
PROFILE_ARCH
        Distinguish machines classes that  have  the same ARCH.  All 		 
       sparc machines have ARCH=sparc but set this to either 'sparc32'
        or 'sparc64'.

Ciaran had suggested pushing PROFILE_ARCH into USE, although that 
implies that x86? = ARCH x86 and not necessarily 'x86-linux' since 
anything running on x86 would have ARCH=x86.

While I think the above is the 'proper' way to do things, it would 
require a massive migration of ebuilds in the tree, and no one has 
volunteered for that task, as well as making sure anything that uses 
'x86' in this case runs on everything running on x86..it becomes quite 
complicated, even if it is the most flexable.

Regardless, I'd like to reach a conclusion about this, was GLEP 47 
submitted to the council for the next meeting?

-Alec Warner

-- 
gentoo-dev@g.o mailing list