12790 – initial 'emerge system' will reemerge gcc

Bug 12790 - initial 'emerge system' will reemerge gcc

Summary: initial 'emerge system' will reemerge gcc

Status:	RESOLVED INVALID

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High minor
Assignee:	Martin Schlemmer (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-12-27 09:57 UTC by Jan Schubert
Modified:	2011-10-30 22:17 UTC (History)
CC List:	1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jan Schubert 2002-12-27 09:57:57 UTC

Just installed 1.4_rc2. As happenend in rc1 bootsrap emerges sys-devel/gcc-3.2.1-r0 
instead of sys-devel/gcc-3.2.1-r6. So 'emerge system' has to emerge gcc for a 3rd 
time! IMHO this is not necessary. Especialy on older machines this would take a long 
time. Beside that the applications build before the current gcc release will not be 
compiled with the current gcc (and may have some failures or less optimizing 
therefore)...

Comment 1 Jan Schubert 2002-12-27 10:05:33 UTC

The same thing with sys-devel/gettext-0.11.5-r1 [0.11.5-r0]

Comment 2 Martin Schlemmer (RETIRED) gentoo-dev

2002-12-27 14:49:20 UTC

Well, bootstrap.sh merge whatever are in stable profile.  Take "~x86" out
of ACCEPT_KEYWORDS, and it wont happen.