Bug 501344

Summary: livecd-creator defaults causes excessive load on mirrors
Product: [Fedora] Fedora Reporter: Mads Kiilerich <mads>
Component: livecd-toolsAssignee: Jeremy Katz <katzj>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: davidz, katzj, lex.lists
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-18 20:28:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mads Kiilerich 2009-05-18 16:11:10 UTC
Description of problem:

The defaults for livecd-creator causes all rpms to be downloaded with yum every time an image is build. 

I realize that this behaviour sometimes is necessary, but it shouldn't be the default. I suggest an option to disable caching instead - and perhaps one to clean the cache, similar to what "yum clean all" does for the running system.

Version-Release number of selected component (if applicable):

livecd-tools-024-1.fc11.i586

Comment 1 Jeremy Katz 2009-05-18 20:28:19 UTC
The default behavior is very intentionally that after running, the only thing different on your filesystem is the addition of the iso you've created.  Leaving around a cache directory is complex (share with yum?  pungi?  some say yes, some say no) and so it's easier to always use temporary space and ensure that we clean up at the end of the process.

If you wish to use a persistent cache directory, you can run with --cachedir and specify where you want to put the cache and then it's up to you to clean it up

Comment 2 lexual 2009-10-31 05:19:45 UTC
Jeremy,

Are you saying that specifying a --cache option will prevent the cache from being deleted.

I just tried a run with --cache=/var/cache/yum and it deleted 5G of files I had there.

Is there currently any way to prevent the cache from being deleted?