* Paul de Vrieze <[EMAIL PROTECTED]>: > On Saturday 06 December 2003 15:11, Alastair Tse wrote: > > > > The solution is to do "emerge portage" instead, but that is also not > > obvious from the output, at least to me. Anyone thinks that putting > > <sys-apps/portage-2.0.49-r16 would be more intuitive to the user than > > actually checking that in pkg_setup()? > > No, as long as you take care that it is not possible to actually merge > python-2.3 with a wrong portage.
It is not possible ;) Okay, today i started a new install. Extracted stage1-x86-20030910.tar.bz2 and did the bootstrap in ARCH. After that i switched to ~ARCH (ARCH is x86). (There is a warning to do it this way in the 'old' installation guide http://www.gentoo.org/doc/en/gentoo-x86-install.xml - btw. i could not find this warning in the handbook. Was this dropped intentionally?) Getting to stage3 let me end with the following dependency problem: # emerge portage -p [ebuild N ] dev-lang/python-2.3.2-r2 [ebuild U ] sys-apps/portage-2.0.49-r18 [2.0.49-r15] But python requires: >=sys-apps/portage-2.0.49-r16 What was the problem here: - should i change to ~ARCH before bootstraping (this should install portage-2.0.49-r18) as the handbook suggests. - shouldnot i change to ~ARCH before 'emerge system'? - should i emerge intermediatly a python-2.2 version? -- .: Regards Torsten | Don't change the reason, just change the excuses! :. -- [EMAIL PROTECTED] mailing list
