Under the Configuring Portage Section it currently says: If you are warned that a new Portage version is available and that you should update Portage, you should do it now using emerge portage command. In order to prevent portage been added to the world file this should be done with --oneshot. Reproducible: Always Steps to Reproduce:
Thanks for reporting; fixed in CVS.
(In reply to comment #0) > > In order to prevent portage been added to the world file this should be done > with --oneshot. > False. Portage doesn't add itself to world file, even if i run "emerge portage" without --oneshot. Try this: # grep sys-apps/portage /var/lib/portage/world <no output> # emerge portage .... .... .... # grep sys-apps/portage /var/lib/portage/world <no output>
(In reply to comment #2) > False. Portage doesn't add itself to world file, even if i run "emerge portage" > without --oneshot. Well, I'll leave the fix as it is in case the behavior changes in the future, when there's more than one supported package manager. You'd think any package explicitly merged without --oneshot *should* be added to world, regardless of what the package is.
Well, --oneshot doesn't hurt ;)
