[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Rule-list] vacuum example
From: |
Marco Fioretti |
Subject: |
Re: [Rule-list] vacuum example |
Date: |
Sat, 30 Nov 2002 09:12:53 +0100 |
User-agent: |
Mutt/1.4i |
On Fri, Nov 29, 2002 23:10:46 at 11:10:46PM -0800, Eugene Wong (address@hidden)
wrote:
>
> As far as I can tell, it would be much better if I can make Vacuum unware
> of install scripts & rpms. This way Vacuum would be good at 1 thing. Any
> other program that wants to make use of it should call it with the
> appropriate arguements.
>
That is OK anyway. There is nothing limiting its usefulness if you
leave to the caller (human or script) the responsibility to tell
exactly to vacuum how it should work. If this turns out too
complicated, the other way is to make it so that vacuum works as you
explained, and something else is written to be used *during* the
install procedure, but:
the two things use the same file lists
What is important is that we use and have to maintain only one list of
files to be removed per package per RH version
emacs_bloat_RH_8.0_20021130
Xfree_bloat_RH_8.0_20021130
etc...
I think to "one list per rpm" so it is easier to match cleaning
actions with packages. The date in the names above is some way to
remember that a bloat list must be updated when the RPM package for RH x.x
has a new release.
So, as long as the format of the bloat lists is thought to support
both cases, we can optimize each tool for each task
Let us know what you find
Ciao, and thanks,
Marco Fioretti