Bug 479907 - FutureFeature: Ability to purge package cache rather than just clean.
Summary: FutureFeature: Ability to purge package cache rather than just clean.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 10
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-13 23:19 UTC by DaveG
Modified: 2014-01-21 23:07 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-01-14 13:53:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description DaveG 2009-01-13 23:19:04 UTC
Description of problem:

FutureFeature - yum
=============

keepcache=1 is useful when removing and installing packages but cache storage grows unconfined. `yum clean packages` is no more useful than `rm -f /var/cache/yum/*/packages/*`. All or nothing.

A "really useful" enhancement would be the ability to clean, but keep the newest 'n' packages, i.e. purge the package cache. e.g.
  yum [purge|clean] --keep=[n]

Ideal candidate for a weekly or monthly cron job.

Version-Release number of selected component (if applicable):
Currently yum-3.2.20-5
How reproducible:
N/A.
Steps to Reproduce:
N/A.
Actual results:
N/A.
Expected results:
N/A.
Additional info:

I have written a utility to perform this task but it's stand-alone and in Perl. Over the life of Fedora 8 it has freed over 2GB of space while keeping the latest versions available.
Let me know if you want a copy - it describes the issue/solution quite well.

Cheers,
--DaveG.

Comment 1 seth vidal 2009-01-14 03:10:26 UTC
you can use repomanage for this:

repomanage -k n -o /var/cache/yum | xargs rm -f

repomanage is in yum-utils

Comment 2 seth vidal 2009-01-14 13:53:36 UTC
Since we have a way to do this and we have lots of ways of making local mirrors, I think I'm going to pass on implementing this inside yum itself.

thanks


Note You need to log in before you can comment on or make changes to this bug.