Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 433373 - Substitute old make.conf path
Summary: Substitute old make.conf path
Alias: None
Product: [OLD] Docs on
Classification: Unclassified
Component: Installation Handbook (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Docs Team
Depends on:
Reported: 2012-08-29 21:57 UTC by torben.hensgens
Modified: 2013-04-07 13:20 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description torben.hensgens 2012-08-29 21:57:42 UTC
For me it seems that there is a inconsistent declaration where the 'make.conf' should reside: on many documentation links in the installation handbook the referred path is '/etc/portage/make.conf' (e.g. on this page: and for instance in the x-org how-to as well (

However, it seems that '/etc/portage/make.conf' takes the priority (read last), but i could not find a statement about 'etc/make.conf' and '/etc/portage/make.conf' in the whole documentation.
And on a fresh and clean installation there's no '/etc/portage/make.conf' for me.

As long as there's no migration, maybe the default system should symlink /etc/make.conf from /etc/portage/make.conf.
Comment 1 Sven Vermeulen (RETIRED) gentoo-dev 2012-10-31 18:52:18 UTC
If the make.conf on a new installation isn't in /etc/portage then that's a bug in the stage file you're using. As far as I know, the stage3 files provide it in the /etc/portage location already.

$ bzgrep make.conf stage3-amd64-20121013.tar.bz2.CONTENTS  
-rw-r--r-- root/root          539 2012-10-13 16:55 ./etc/portage/make.conf
-rw-r--r-- root/root          539 2012-10-13 15:35 ./etc/portage/make.conf.catalyst
-rw-r--r-- root/root        12652 2012-10-13 16:50 ./usr/share/man/man5/make.conf.5.bz2
-rw-r--r-- root/root        19369 2012-10-13 16:50 ./usr/share/portage/config/make.conf.example

If you notice any reference to /etc/make.conf anywhere, I'd be glad to fix it. But I don't see a need to document the old location.