[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: yum clean bug



Jeff Spaleta wrote:
> On 12/8/05, Neal Becker <ndbecker2 gmail com> wrote:
>> Perhaps "disabled" should be split into multiple options?  disable-install,
>> disable-clean, etc?
> 
> 
> dear god... that level of command granularity is madness.. absolute madness.
> 
> +1
> for adding text in the manpage which states that if you want to clean
> to act on all configured repositories  to --enablerepo=*  during clean
> operations.

If you've asked "all" in the first place that was precisely to nuke
everything no questions asked. You didn't ask about particular repos,
you asked yum to clean all its temp data

Also, the FHS states clearly :

« /var/cache is intended for cached data from applications. Such data is
locally generated as a result of time-consuming I/O or calculation. The
application must be able to regenerate or restore the data. Unlike
/var/spool, the cached files can be deleted without data loss. »

So if the yum cache must be preserved to prevent data loss (as Seth
writes), it has no place in /var/cache. It can be nucked at any time by
yum or something else (« The application must always be able to recover
from manual deletion of these files (generally because of a disk space
shortage »).

yum clean all behaviour may be familiar to yum developpers, but it's
contrary to both English (all is no longer everything) and accepted
Linux standards (cache is no longer disposable)

-- 
Nicolas Mailhot


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]