If portage is goning to be upgraded durring an emerge, a message appears in the emerge -p display that says that after portage is upgraded the dependencies will be recalculated. Perhaps portage should be "bumped" to the top of the list so everything uses the new and (hopefully) improved portage. I ususaly manualy run an emerge portage before any update, but i think this should be automatic if portage was in the list of things to be updated. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Fixed.
Released in 2.1_pre2.
Hi. Hmmm, this isn't fixed for me with neither _pre2 nor _pre3. Haven't tested with _pre3-r1. Ahh wait, upon further investigation it doesn't work with --deep, only with --pretend. So shouldn't portage be on top of the list with --deep also? Thanks, Max
No, portage can't be forced to be the first item on the list because portage has its own dependencies. What has changed is that portage is forced to the top of the list of atoms that need to be checked.
