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