On Thu, 2003-12-11 at 10:44, Torsten Veller wrote: > # 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]
You sure you're not doing "emerge -up portage" ? bash-2.05b# emerge -p portage [snip..] Calculating dependencies ...done! [ebuild U ] sys-apps/portage-2.0.49-r18 [2.0.49-r10] bash-2.05b# emerge -up portage [snip..] [ebuild N ] dev-lang/python-2.3.2-r2 [ebuild U ] sys-apps/portage-2.0.49-r18 [2.0.49-r10] > But python requires: >=sys-apps/portage-2.0.49-r16 Yes, otherwise things will break. Just "emerge portage" will get you portage and not python. Unless the version of python on your image is not available. > What was the problem here: > - should i change to ~ARCH before bootstraping (this should install > portage-2.0.49-r18) as the handbook suggests. I don't know what we support now. I've never thought of this as a good idea. But we allow people to do it, and we don't guarantee that things will not break if you do so. ~ARCH is mainly for testing. If you want a system up and running, you should try without ~ and then upgrade from there. > - should i emerge intermediatly a python-2.2 version? In fact, because you can already run portage, it implies you have python-2.2.x installed. That is from the bootstrap image or one of the stages. Until we have stages with 2.3, you will need to have python2.2. I'm not sure how those stages are built. I've tried using the old stager but couldn't get what I wanted, and I've yet to try catalyst. You may want to follow this bug: http://bugs.gentoo.org/show_bug.cgi?id=35525 Cheers, -- Alastair 'liquidx' Tse >> Gentoo Linux Developer >> http://www.liquidx.net/ | http://dev.gentoo.org/~liquidx/
signature.asc
Description: This is a digitally signed message part
