[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.
>
> -jef"snow before morning rush hour good... snow during morning rush
> hour bad"spaleta
>
>   
There are *exactly* two courses of action I would stand behind:

1.  Improving documentation to cover what 'yum clean' is and is not. 
Including further directions for those who want a sterile cache would be
sensible.
2.  Creating a separate tool or adding the capability to yum to
'sanitize' the cache folder, which would mean *completely* cleaning it out.

#1 is easy enough.  Anyone can do this, and it would take less effort
than continuing this discussion.
#2 is just a matter of where it should go.  If Seth feels really nice,
it might be able to go into yum as a command (eg. 'yum sanitize' or 'yum
clean --sanitize'), but otherwise would need to be created as a plugin
or separate tool (possibly to be included in yum-utils).  This option
would still be well-served by #1.  I personally don't have time to
undertake this, but I'd be happy to advise anyone who is to the best of
my abilities.

-- 
Patrick "The N-Man" Barnes
nman64 n-man com

http://www.n-man.com/
-- 
Rate my assistance!  http://rate.affero.net/nman64/


Attachment: signature.asc
Description: OpenPGP digital signature


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