4585955a8b
Every run we are doing a full tar.gz of the chroot environment that never gets used. It's not suitable for CI since we use fresh images each time there. The cache in general isn't really isn't a very safe thing to have around, because there's no invalidation procedure and no real way to make one -- we've no guarantee that a new chroot build even moments after a previous one wouldn't bring in or different packages, etc (of course this is *unlikely*, but the longer you go between builds the worse the problem becomes. Also, tons of packages get installed after this not from any cache, so potential speed-up is rather marginal. Debian turned this off with I58fc485aacacaa17243bf9ce760ed91256d1f182. However, given the reasons above and it's complete lack of testing, I don't see this as useful. If we really want this type of thing, I think we should come up with a way to use a persistent external yum/dnf cache that yum/dnf keeps in sync with it's usual invalidation rules. Change-Id: I66789c35db75c41bc45ea1ad2e26f87456de4e4d
15 lines
555 B
ReStructuredText
15 lines
555 B
ReStructuredText
===========
|
|
yum-minimal
|
|
===========
|
|
Base element for creating minimal yum-based images.
|
|
|
|
This element is incomplete by itself, you'll want to use the centos-minimal
|
|
or fedora-minimal elements to get an actual base image.
|
|
|
|
Use of this element will require 'yum' and 'yum-utils' to be installed on
|
|
Ubuntu and Debian. Nothing additional is needed on Fedora or CentOS.
|
|
|
|
If you wish to have DHCP networking setup for eth0 & eth1 via
|
|
/etc/sysconfig/network-config scripts/ifcfg-eth[0|1], set the
|
|
environment variable `DIB_YUM_MINIMAL_CREATE_INTERFACES` to `1`.
|