public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sami Dalouche" <skoobi@free.fr>
To: "'Andy Arbon'" <gentoo@andrewarbon.co.uk>,
	"'gentoo-dev'" <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] Cruft detecting script
Date: Mon, 3 Mar 2003 20:19:21 +0100	[thread overview]
Message-ID: <000201c2e1b9$cd4118b0$c701a8c0@bluefire> (raw)
In-Reply-To: <3E6234DF.104@andrewarbon.co.uk>

Hi,

It seems everybody agrees to make a configurable exclude-list for your 
Script.
What I suggest is that you take the debian "cruft" package, and modify 
It so that it works with gentoo.
The way it works is easy :
 1) produces a list of every file in the system (find /)
 2) runs every script in /etc/cruft/exclude/ (or whatever)
 3) remove 2 from 1
 4) remove all package-owned files from 1)
 5) print the rest

As a result, you can configure the files you want excluded by creating
simple
#!/bin/sh
find /usr/local

Scripts, for example..


Sam

> -----Original Message-----
> From: Andy Arbon [mailto:gentoo@andrewarbon.co.uk] 
> Sent: dimanche 2 mars 2003 17:44
> To: gentoo-dev
> Subject: [gentoo-dev] Cruft detecting script
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> 
> I've been wondering about writing a cruft detecting script.. 
> The basic idea would be:
> * Produce a list of every file that Portage claims 
> responsibility for on the current system (ie. the results of 
> qpkg -l `qpkg -I`)
> * Produce a list of every file in the system (ie. find /)
> * Remove the first set from the second
> * Whatever's left is 'cruft'
> 
> The above needs to be tweaked so that find doesn't look in 
> areas that are not used for system things, eg. /home, /tmp etc.
> 
> Has anyone written something like this, and does anyone have 
> any reason why something like this wouldn't work or be useful?
> 
> Cheers,
> 
> Andy
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQE+YjTeX3TTUvZURBERAhcmAKCgpIMVRugO9gbeKvTKG+TgObI0pgCeO4fb
> bRqkUTm51aLUB8/Lpn5J1BQ=
> =4xNI
> -----END PGP SIGNATURE-----
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 
> 
> 


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-03-03 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-02 16:44 [gentoo-dev] Cruft detecting script Andy Arbon
2003-03-02 17:12 ` Brian Jackson
2003-03-02 18:05   ` Mark Gordon
2003-03-03  8:41     ` Ian Phillips
2003-03-03 15:22     ` Gareth John
2003-03-03 19:19 ` Sami Dalouche [this message]
2003-03-03 23:06 ` Evan Powers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000201c2e1b9$cd4118b0$c701a8c0@bluefire' \
    --to=skoobi@free.fr \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo@andrewarbon.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox