On Thursday 09 March 2006 20:37, Grobian wrote:
> As far as I know: no. I didn't myself because I'm having a problem with
> ppc-macos and the upcoming x86-macos (they will probably have a lot in
> common) and am not completely sure whether what Diego and I proposed is
> actually flexible enough.
I
On 09-03-2006 12:30:33 -0500, Alec Warner wrote:
> Regardless, I'd like to reach a conclusion about this, was GLEP 47
> submitted to the council for the next meeting?
As far as I know: no. I didn't myself because I'm having a problem with
ppc-macos and the upcoming x86-macos (they will probably h
Stephen Bennett wrote:
On Thu, 09 Mar 2006 10:20:33 -0500
Alec Warner <[EMAIL PROTECTED]> 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 ha
On Thursday 09 March 2006 16:20, Alec Warner 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 ).
Right now ARCH=x86-fbsd for G/FBSD, as spb already said, so it's not much of
the problem.
If that will change
On Thu, 9 Mar 2006 15:29:23 +0100
"Diego 'Flameeyes' Pettenò" <[EMAIL PROTECTED]> wrote:
> To bring ~x86-fbsd keywording in main tree, we mainly need to move a
> true profile in the tree, not a dummy one, mark it as indev and start
> the keywording. (I've already cleaned up the default-bsd/fbsd pr
On Thu, 09 Mar 2006 10:20:33 -0500
Alec Warner <[EMAIL PROTECTED]> 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 elsew
Diego 'Flameeyes' Pettenò wrote:
> Okay, solar asked me yesterday, and I think this might be the good moment to
> start this out.
> Right now the x86-fbsd keyword is not being used in the main tree, and the
> whole Gentoo/FreeBSD is handled in an overlay, sharing the ~x86 keyword with
> standard
Okay, solar asked me yesterday, and I think this might be the good moment to
start this out.
Right now the x86-fbsd keyword is not being used in the main tree, and the
whole Gentoo/FreeBSD is handled in an overlay, sharing the ~x86 keyword with
standard Gentoo/Linux.
Unfortunately this has a ser