Bug 108669 – advice to ignore portage update before emerge --emtytree doubles initial build time

• Product: [OLD] Docs-user
• Status: RESOLVED INVALID

[Description Liam Widdess 2005-10-09 15:34:01 UTC]

Users are instructed on this page to ignore emerge's warning to update the
portage tree if a new version is found after the initial emerge --sync,
prior to the initial emerge of system during an install. There is no good
reason for this, in fact this causes emerge --emptytree to be run again
recursively from the top when it hits portage, which is well over half way
through the build - nearly doubling the initial install time! When I saw
what was happening I interrupted the emerge and ran emerge system, which
even let some packages slip through from stage2 without an initial compile
(not sure if I should be grateful or fearful about that one ;)

This advice should probably be changed.


Reproducible: Always
Steps to Reproduce:
1. Install a stage 2 tarball
2. Wait for emerge --sync to show up a new portage version
3. Ignore the warning to emerge portage and follow these instuctions instead


Actual Results:  
I nearly died of boredom ;)

[Comment 1 Sven Vermeulen (RETIRED) 2005-10-09 20:57:59 UTC]

I would be surprised if "emerge -e system" would start over when emerging
Portage. Normally, emerge will build all tools depending on Portage, then
Portage and then reload the Portage configuration, but it will /resume/ the
"emerge -e system", not repeat it. Otherwise, it would be in an endless loop.

[Comment 2 Sven Vermeulen (RETIRED) 2005-10-21 13:37:59 UTC]

emerge -e system doesn't restart.