| 1 |
On Sun, 2 Mar 2003 11:12:40 -0600 |
| 2 |
Brian Jackson <brian@××××.com> wrote: |
| 3 |
|
| 4 |
> On Sunday 02 March 2003 10:44 am, Andy Arbon wrote: |
| 5 |
|
| 6 |
> > I've been wondering about writing a cruft detecting script.. The |
| 7 |
> > basic idea would be: |
| 8 |
> > * Produce a list of every file that Portage claims responsibility |
| 9 |
> > for on the current system (ie. the results of qpkg -l `qpkg -I`) |
| 10 |
> > * Produce a list of every file in the system (ie. find /) |
| 11 |
> > * Remove the first set from the second |
| 12 |
> > * Whatever's left is 'cruft' |
| 13 |
> > |
| 14 |
> > The above needs to be tweaked so that find doesn't look in areas |
| 15 |
> > that are not used for system things, eg. /home, /tmp etc. |
| 16 |
> > |
| 17 |
> > Has anyone written something like this, and does anyone have any |
| 18 |
> > reason why something like this wouldn't work or be useful? |
| 19 |
> |
| 20 |
> I think this could be very useful to some, but not very useful for |
| 21 |
> others. I often install software not using an ebuild, so for me it |
| 22 |
> would detect some of the stuff that I installed without an ebuild. |
| 23 |
|
| 24 |
Exclude /usr/local as well. That should exclude most software not |
| 25 |
installed through portage. Possibly use a config file so that other |
| 26 |
directories can be excluded by the user. |
| 27 |
|
| 28 |
I think it would be useful for people who know what they are doing, |
| 29 |
dangerous for people who only *think* they know what they are doing. |
| 30 |
-- |
| 31 |
Mark Gordon |
| 32 |
Paid to be a Geek & a Senior Software Developer |
| 33 |
Currently looking for a new job commutable from Slough, Berks, U.K. |
| 34 |
Although my email address says spamtrap, it is real and I read it. |
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-dev@g.o mailing list |
Archives