Gentoo Archives: gentoo-dev

From: Marius Mauch <genone@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Why arch-specific make.conf files?
Date: Tue, 15 Nov 2005 19:22:31
Message-Id: 20051115201919.11d52815@sven.genone.homeip.net
Hi,

Was just about to finally commit the elog related config stuff into
make.conf just to notice (again) that there are 14 (in words: fourteen)
different make.conf files there, with almost all of them just differing
in CFLAGS and CHOST (only exception is make.conf.mac which isn't used
anymore in any way AFAICT).
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.
So what's the general opinion about this? Having all these different
files makes it harder to add config changes, not by much but noticably,
so personally I'd like to get rid of them, but if there is a good
reason for them to stay I can live with that.

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-dev] Why arch-specific make.conf files? "Diego 'Flameeyes' Pettenò" <flameeyes@g.o>
Re: [gentoo-dev] Why arch-specific make.conf files? Chris Gianelloni <wolf31o2@g.o>
Re: [gentoo-dev] Why arch-specific make.conf files? Chris Gianelloni <wolf31o2@g.o>
Re: [gentoo-dev] Why arch-specific make.conf files? Gustavo Zacarias <gustavoz@g.o>