yum clean bug

[Jesse Keating]

On Fri, 2005-12-09 at 19:00 +0100, Nicolas Mailhot wrote:
> " The application must always be able to recover from manual deletion of
> these files "

Yum can.  How is this relevant?

> So other stuff does not need to notify the app that wrote those files
> before deleting them

How can you extrapolate that meaning?  Must be able to recover == can
delete w/out notification?  Some apps will react rather strangely if you
delete the cache they're working from in the middle of an operation...

> " (generally because of a disk space shortage) "
> 
> So when the system / the admin wants to reclaim some disk space, it's /
> he's allowed to do a find /var/cache -type f -exec -rm -f \{\} \;

Nothing is stopping the admin from doing this now.  Typically the admin
should know what the heck they are doing when doing rm -f actions.  One
would typically not do this whilst yum or some other app is running
actively and using the cache.

> Actually it goes even farther than this, other stuff don't have to give
> any particular reason to delete files in /var/cache.
> 
> Any package may include such a bit in its install scriplets and it'll be
> perfectly legit.
> 

And most likely would never ever get distributed with this bit enabled.
Wholesale remove of other's cache items is ridiculous and wouldn't get
included anywhere.

Nowhere in here do I see any argument that states yum should make
assumptions on the user's part about when to remove files not associated
with an existing/enabled repository.  Do you actually have a valid
argument for this feature, or are you just making noise?

-- 
Jesse Keating RHCE      (geek.j2solutions.net)
Fedora Legacy Team      (www.fedoralegacy.org)
GPG Public Key          (geek.j2solutions.net/jkeating.j2solutions.pub)
 
Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=jkeating