From: Stephen Bennett <spb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] x86-fbsd keyword in main tree?
Date: Thu, 9 Mar 2006 15:31:58 +0000 [thread overview]
Message-ID: <20060309153158.76e1a8a2@localhost> (raw)
In-Reply-To: <441047C1.1020102@gentoo.org>
On Thu, 09 Mar 2006 10:20:33 -0500
Alec Warner <antarus@gentoo.org> 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.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-09 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 14:29 [gentoo-dev] x86-fbsd keyword in main tree? Diego 'Flameeyes' Pettenò
2006-03-09 15:20 ` Alec Warner
2006-03-09 15:31 ` Stephen Bennett [this message]
2006-03-09 17:30 ` Alec Warner
2006-03-09 19:37 ` Grobian
2006-03-09 20:21 ` Diego 'Flameeyes' Pettenò
2006-03-09 15:42 ` Diego 'Flameeyes' Pettenò
2006-03-09 15:44 ` Stephen Bennett
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=20060309153158.76e1a8a2@localhost \
--to=spb@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