From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Why arch-specific make.conf files?
Date: Tue, 15 Nov 2005 14:55:13 -0500 [thread overview]
Message-ID: <1132084514.9703.46.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <20051115201919.11d52815@sven.genone.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Tue, 2005-11-15 at 20:19 +0100, Marius Mauch wrote:
> From my POV those vars should be set in the profiles instead, and a
> quick scan shows that indeed most (maybe all? didn't count them)
> profiles set them already, so there isn't really a point in having them
> in make.conf too, except to make it easy for users to change them. For
> CHOST this seems to be a bad idea, not sure about CFLAGS.
Oh yeah, if you happen to change any of this stuff, please be sure to
inform the catalyst team, along with Release Engineering. We don't want
something like this surprising us when we're in the middle of release
building.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-15 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 19:19 [gentoo-dev] Why arch-specific make.conf files? Marius Mauch
2005-11-15 19:26 ` Diego 'Flameeyes' Pettenò
2005-11-15 19:54 ` Chris Gianelloni
2005-11-16 2:30 ` Marius Mauch
2005-11-16 12:50 ` Chris Gianelloni
2005-11-16 15:04 ` Marius Mauch
2005-11-16 17:47 ` [gentoo-dev] " Duncan
2005-11-15 19:52 ` [gentoo-dev] " Chris Gianelloni
2005-11-15 20:01 ` Mike Frysinger
2005-11-15 21:01 ` Chris Gianelloni
2005-11-15 21:12 ` Mike Frysinger
2005-11-16 2:40 ` Marius Mauch
2005-11-15 19:55 ` Chris Gianelloni [this message]
2005-11-16 17:18 ` Gustavo Zacarias
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=1132084514.9703.46.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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