1 |
On Thu, Sep 25, 2008 at 3:15 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> On Thursday 25 September 2008 17:51:58 Daniel Pielmeier wrote: |
3 |
>> > Do you have any further advice, more detail or some more formalized |
4 |
>> > methodology to 'clean' the world file, in addition to what you have |
5 |
>> > stated above? |
6 |
>> |
7 |
>> Every entry in the world file that has a reverse dependency could be |
8 |
>> removed. Unfortunately there is no tool I know which can calculate |
9 |
>> reverse dependencies correctly. Maybe there is some functionality in |
10 |
>> pkgcore or paludis which I am not aware of. So others need to inform |
11 |
>> us about this. |
12 |
> |
13 |
> The loooooong way round is to run 'emerge -pvte world' and look for things |
14 |
> listed that are both highlighted in green and indented. Such packages could |
15 |
> in theory be removed from world as they must be a dep of something. |
16 |
> |
17 |
> Intelligence must also be applied of course - somethings are deps and you DO |
18 |
> want them in world |
19 |
|
20 |
Yes, basically my philosophy is only to list in world the actual |
21 |
programs I want to use. Everything else required for them will come in |
22 |
automatically (assuming I also set my USE flags in package.use |
23 |
properly). Some packages have optional run-time deps, say a multimedia |
24 |
program that can convert files if you have ffmpeg installed, so in |
25 |
those cases those optional packages will also be in world. |
26 |
|
27 |
Learning when to use --oneshot and when not was the key to keeping |
28 |
away the clutter :) |