From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Preventing $ARCH flags in USE
Date: Wed, 17 Sep 2008 09:19:49 -0700 [thread overview]
Message-ID: <48D12E25.8000003@gentoo.org> (raw)
In-Reply-To: <48CEBB5B.8020507@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Vlastimil Babka wrote:
> Apparently, setting USE=x86 in make.conf on amd64 arch can have funny
> consequences such as [1]. And I can imagine even more subtle and hard to
> detect errors due to this.
>
> I think it's better to prevent this rather than waste time with bug
> reports like that. I asked Zac on IRC whether portage could filter such
> flags. He suggested using use.mask in profiles. Well since ARCH is also
> set by a profile, why not. Although a really persistent and stupid user
> could use.unmask, it's better than no protection. And then we can think
> how to replace the current ARCH->USE flag system with e.g. USE_EXPAND.
> What do you think?
>
> Vlastimil
>
> [1] http://bugs.gentoo.org/show_bug.cgi?id=236801
>
I suggest that we unmask the appropriate ARCH flags in
profiles/arch/*/use.mask, add ../base to profiles/arch/*/parent, and
create profiles/arch/base/use.mask to mask all of the existing ARCH
flags. This will serve to mask all but the appropriate ARCH flags
for all of the 2008.0 profiles. Does this seem reasonable?
- --
Thanks,
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkjRLiMACgkQ/ejvha5XGaOUnACfb+wsK5BbVdNgmuG/KShxDPXy
hUUAn2a4hwO+4euOmExozx+7MegJZLK7
=9/4W
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-09-17 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 19:45 [gentoo-dev] Preventing $ARCH flags in USE Vlastimil Babka
2008-09-15 20:01 ` Santiago M. Mola
2008-09-15 20:20 ` Zac Medico
2008-09-16 6:01 ` Fabian Groffen
2008-09-16 6:05 ` Ciaran McCreesh
2008-09-17 15:07 ` Zac Medico
2008-09-17 16:19 ` Zac Medico [this message]
2008-09-28 16:19 ` Donnie Berkholz
2008-09-28 16:32 ` Zac Medico
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=48D12E25.8000003@gentoo.org \
--to=zmedico@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