Mark Knecht wrote:
As part of emerge -DuN system portage appears to first make me remove
python by hand. Is this safe?
Thanks,
Mark
dragonfly ~ # emerge -pvDuN -1 python-updater
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] app-admin/python-updater-0.5 [0.2] 6 kB
[ebuild U ] sys-devel/autoconf-2.61-r2 [2.61-r1] USE="-emacs" 0 kB
[ebuild U ] perl-core/Test-Harness-3.10 [2.64] 173 kB
[ebuild NS ] dev-lang/python-2.5.2-r5 USE="berkdb gdbm ipv6
ncurses readline ssl threads tk -bootstrap -build -doc -examples
-sqlite -ucs2 -wininst" 9,597 kB
[ebuild U ] net-misc/rsync-3.0.2 [2.6.9-r6] USE="acl iconv%* ipv6
-static -xattr% -xinetd" 748 kB
[blocks B ] <dev-lang/python-2.3.6-r2 (is blocking
app-admin/python-updater-0.5, app-admin/python-updater-0.2)
Total: 5 packages (4 upgrades, 1 in new slot, 1 block), Size of
downloads: 10,523 kB
dragonfly ~ #
No! Not until you get a working version installed. Portage needs
python. Someone correct me if I misstep here:
emerge the new python, run the python updater and let it emerge whatever
packages it needs to rebuild, check to make sure nothing still needs the
old version and then you can unmerge the old one.
I think that is the correct way.
It is also safer to keep a spare copy of some things around in case you
mess up to. man make-conf and look for buildsyspkg.
Dale
:-) :-)
