Bug 34503

Summary:	after stage1 install, and a portage update, there is still the old make.conf
Product:	Portage Development	Reporter:	Clemens Schwaighofer <gullevek>
Component:	Unclassified	Assignee:	Portage team <dev-portage>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Clemens Schwaighofer 2003-11-27 01:36:24 UTC

when I install from stage1 (1.4 final cd) I have a quite old make.conf (not 
all options are inside). of course during the base install (system) I install 
a new portage. but the new make.conf is never applied. So although I have a 
up2date portage I still have an old make.conf (no portage exclude, mirrors, 
etc). 

Reproducible: Always
Steps to Reproduce:
1. emerge system 
2. new portage is installed but make.conf stays the original  one 
3.

Comment 1 Marius Mauch (RETIRED) gentoo-dev

2003-11-27 03:34:27 UTC

did you run etc-update ?

Comment 2 Andrew Bevitt 2003-11-27 06:37:32 UTC

More precisely did you emerge portage before running bootstrap.sh
http://www.gentoo.org/doc/en/gentoo-x86-install.xml#doc_chap9

chroot, sync, update portage, setup make.conf ...

In this manner make.conf is not protected, and hence overridden by 
emerge portage. I dont think this is a bug at all...

Comment 3 Clemens Schwaighofer 2003-11-27 17:14:12 UTC

emerge sync; configre make.conf; bootstrap; emerge system.

I actually emerged portage after bootstrap; but I think I might have left the flag "protect or so". might be my mistace at all at the end ...

but how can I get the new make.conf? shall I reemerge portage?

Comment 4 Nicholas Jones (RETIRED) gentoo-dev

2003-12-10 06:34:20 UTC

make.conf is now installed as make.conf.orig.