1 |
On Mon, 02 Mar 2015 09:29:15 -0500, Tanstaafl wrote: |
2 |
|
3 |
> > Yes, you shouldn't really have any libs in your world file. Any |
4 |
> > required would be pulled in as dependencies. |
5 |
> |
6 |
> Is this in fact true? |
7 |
|
8 |
Yes. The world file is for the software you want installed. Portage will |
9 |
take care of its dependencies. Putting dependencies in world stops |
10 |
portage doing its job properly and can cause blockers at a leter dTE. |
11 |
|
12 |
> |
13 |
> I checked mine, and found: |
14 |
> |
15 |
> # grep -i libs /var/lib/portage/world |
16 |
[LOTS] |
17 |
> |
18 |
> So, should I delete all of these? Even glib and glibc? |
19 |
|
20 |
Absolutely, especially glibc. When was the last time YOU used glibc, it |
21 |
is a dependencies, not a user application. |
22 |
|
23 |
> Also - is there a definitive guide (preferably for non programmer types) |
24 |
> on just how to properly clean the world file? |
25 |
|
26 |
Load it into an editor and remove everything that you do not run yourself, |
27 |
or need as a startup daemon in the case of a server. |
28 |
|
29 |
The run emerge --depclean -p and read the output carefully. If there is |
30 |
anything in there you need, add it with emerge -n pkgname and run |
31 |
depclean again. |
32 |
|
33 |
Rinse and repeat until depclean shows only packages you know you don't |
34 |
need yourself, then run it again without -p. |
35 |
|
36 |
|
37 |
-- |
38 |
Neil Bothwick |
39 |
|
40 |
Secret hacker rule #11: hackers read manuals. |