1 |
On Mon, January 26, 2009 18:35, Grant wrote: |
2 |
>>> What do you guys think of this? Do you know of a good cruft removal |
3 |
>>> script? |
4 |
>> |
5 |
>> Yep, there's quite good one in gentoo itself. |
6 |
>> |
7 |
>> Basically, you'll need to write a short config for it, consisting of |
8 |
>> lines like "cruft name", "cruft src uri" and a few more lines if you'll |
9 |
>> need to pass some extra parameters to configure/make/install. |
10 |
>> It'll build the package in a sandbox, then transfer it to destination, |
11 |
>> memorizing every change it did and preventing collisions and config |
12 |
>> overwrites. |
13 |
>> |
14 |
>> Just put that config script into an ebuild file and use portage to |
15 |
>> build it - as simple as it gets ;) |
16 |
> |
17 |
> I suppose you and Jesus are right, but what about cruft removal? Are |
18 |
> you saying Gentoo is 100% cruft-free? I've got a lot of junk in /etc |
19 |
> and especially ~/.* |
20 |
|
21 |
No. It isn't 100% free. |
22 |
|
23 |
Emerge will only remove the stuff it installed. There's absolutely no way |
24 |
to guarantee that any file in /etc is not needed any longer. Besides that: |
25 |
|
26 |
1.- YOU created those files, so you are the one that should keep the track |
27 |
of them |
28 |
2.- They are not part of the package, emerge will only uninstall what it |
29 |
installed, |
30 |
nothing else, I would be very angry if a silly package manager starts |
31 |
deleting files |
32 |
I created by hand. |
33 |
3.- you might want to install that package again, and you are probably not |
34 |
willing |
35 |
to reconfigure it again |
36 |
4.- seriously, even three thousand of files in /etc are not a problem. |
37 |
They take |
38 |
a few bytes or several kb at most. You better look at /usr/src or the |
39 |
number of |
40 |
installed games and/or icon themes. |
41 |
|
42 |
In the rest of the three there shouldn't be too much cruft if you stick to |
43 |
portage and don't go installing things by hand around (if you do then you |
44 |
can't blame portage neither). |
45 |
|
46 |
Cruft removers base their actions on guesses. I never felt like those |
47 |
programs |
48 |
really worked at all. If you use one of them you have still to review the |
49 |
final list |
50 |
before removal (that or you are good at making backups, you know). So I don't |
51 |
know what the point is. I would be quicker to clean the tree myself using |
52 |
mc and |
53 |
some bash magic. |
54 |
|
55 |
|
56 |
-- |
57 |
Jesús Guerrero |