[PATCH] default to using a global livecd yum cache, not a private one

[Colin Walters]

Hi,

This patch moves the yum cache into /var/cache/livecd so that out of the
box, the tool doesn't repeatedly download stuff from the internet.

[Jeremy Katz]

On Tue, 2007-08-07 at 16:07 -0400, Colin Walters wrote:
>  This patch moves the yum cache into /var/cache/livecd so that out of
> the
>  box, the tool doesn't repeatedly download stuff from the internet. 
Patch is empty :)  But going from the earlier patch you put in bugzilla,
I know the gist of this.  And it's along a similar line as kanarip's
patch to allow specifying the cache dir.  The question is are we better
off just going with a global one always or allowing it to be specified
and if you want to share, then you can specify the global one.  And I
can see both sides, although I somewhat lean towards allowing it to be
specified.

One thing that becomes tricky in either case is how do we handle
cleaning the directory?  Currently, it's simple -- it gets blown away
every time.  When doing a shared or global cache, you don't want to blow
it away, but you also want to make it easy for people to regain the disk
space.  Maybe the answer is that if you specify the cache, then we don't
blow it away and otherwise we do.  Other opinions?

Jeremy

[Bill Nottingham]

Jeremy Katz (katzj(a)redhat.com) said: 
>  On Tue, 2007-08-07 at 16:07 -0400, Colin Walters wrote:
>  > This patch moves the yum cache into /var/cache/livecd so that out of the
>  > box, the tool doesn't repeatedly download stuff from the internet.
>  
>  Patch is empty :)  But going from the earlier patch you put in bugzilla,
>  I know the gist of this.  And it's along a similar line as kanarip's
>  patch to allow specifying the cache dir.  The question is are we better
>  off just going with a global one always or allowing it to be specified
>  and if you want to share, then you can specify the global one.  And I
>  can see both sides, although I somewhat lean towards allowing it to be
>  specified.
>  
>  One thing that becomes tricky in either case is how do we handle
>  cleaning the directory?  Currently, it's simple -- it gets blown away
>  every time.  When doing a shared or global cache, you don't want to blow
>  it away, but you also want to make it easy for people to regain the disk
>  space.  Maybe the answer is that if you specify the cache, then we don't
>  blow it away and otherwise we do.  Other opinions? 
Surely you'd want to unify the yum caches among pungi and livecd-creator?

Bill

[Colin Walters]

On Tue, 2007-08-07 at 16:07 -0400, Colin Walters wrote:
>  Hi,
>  
>  This patch moves the yum cache into /var/cache/livecd so that out of the
>  box, the tool doesn't repeatedly download stuff from the internet.