1 |
On 5/30/07, Ric de France <rdefrance@×××××.com> wrote: |
2 |
|
3 |
> I think what is more useful is --prune (I'm guessing as I'm not in |
4 |
> front of a Gentoo box at the moment). I usually try: |
5 |
> |
6 |
> # emerge -Pp |
7 |
|
8 |
Here's the output: |
9 |
________________________________________ |
10 |
myhost etc # emerge -Pp |
11 |
|
12 |
>>> These are the packages that would be unmerged: |
13 |
|
14 |
dev-java/java-config |
15 |
selected: 2.0.32 |
16 |
protected: 1.3.7 |
17 |
omitted: none |
18 |
|
19 |
sys-devel/automake |
20 |
selected: 1.10 1.6.3 1.7.9-r1 |
21 |
protected: 1.9.6-r2 |
22 |
omitted: none |
23 |
|
24 |
sys-devel/autoconf |
25 |
selected: 2.61 |
26 |
protected: 2.13 |
27 |
omitted: none |
28 |
|
29 |
>>> 'Selected' packages are slated for removal. |
30 |
>>> 'Protected' and 'omitted' packages will not be removed. |
31 |
________________________________________ |
32 |
|
33 |
But doesn't --prune just remove all but the most recent installation |
34 |
of a given package? |
35 |
|
36 |
While on the subject, I ran a pretend on revdep-rebuild, and it's |
37 |
complaining about some broken libraries in GCC... |
38 |
________________________________________ |
39 |
langevin etc # revdep-rebuild -p -v |
40 |
Configuring search environment for revdep-rebuild |
41 |
|
42 |
Environment mismatch from previous run, deleting temporary files... |
43 |
|
44 |
Checking reverse dependencies... |
45 |
|
46 |
Packages containing binaries and libraries broken by a package update |
47 |
will be emerged. |
48 |
|
49 |
Collecting system binaries and libraries... done. |
50 |
(/root/.revdep-rebuild.1_files) |
51 |
|
52 |
Collecting complete LD_LIBRARY_PATH... done. |
53 |
(/root/.revdep-rebuild.2_ldpath) |
54 |
|
55 |
Checking dynamic linking consistency... |
56 |
broken /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcjawt.la (requires |
57 |
/usr/lib/lib-gnu-java-awt-peer-gtk.la) |
58 |
broken /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgij.la (requires |
59 |
/usr/lib/libgcj.la) |
60 |
done. |
61 |
(/root/.revdep-rebuild.3_rebuild) |
62 |
|
63 |
Assigning files to ebuilds... done. |
64 |
(/root/.revdep-rebuild.4_ebuilds) |
65 |
|
66 |
Evaluating package order... done. |
67 |
(/root/.revdep-rebuild.5_order) |
68 |
|
69 |
All prepared. Starting rebuild... |
70 |
emerge --oneshot -p -v =sys-devel/gcc-4.1.2 |
71 |
|
72 |
These are the packages that would be merged, in order: |
73 |
|
74 |
Calculating dependencies... done! |
75 |
[ebuild R ] sys-devel/gcc-4.1.2 USE="fortran gcj gtk mudflap nls |
76 |
(-altivec) -bootstrap -build -d -doc (-hardened) (-ip28) (-ip32r10k) |
77 |
(-multilib) -multislot (-n32) (-n64) -nocxx -objc -objc++ -objc-gc |
78 |
-test -vanilla" 0 kB |
79 |
|
80 |
Total: 1 package (1 reinstall), Size of downloads: 0 kB |
81 |
Now you can remove -p (or --pretend) from arguments and re-run revdep-rebuild. |
82 |
________________________________________ |
83 |
|
84 |
I'm a little uneasy doing a --oneshot emerge of GCC when I just |
85 |
recompiled my system twice... I'm not sure how that will affect my |
86 |
GCC upgrades in the future. I only upgraded a minor version of GCC, |
87 |
too. Any thoughts? |
88 |
-- |
89 |
gentoo-user@g.o mailing list |