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