On Thu, 2006-05-11 at 09:36 -0500, Clark Williams wrote: > > As I mentioned to matt, Jochen, from several months ago, wrote a patch > > to do manual creation of a cached chroot so we could simply copy that > > image into place if it exists and run a 'yum update' on it to make sure > > it is current. > > I remember seeing it in the archives. Do you think we should look at > merging that patch into the current yum?
into yum? it doesn't need to go into yum. The feature need only be added to mock. > My situation is a bit strange, since I use mock to maintain a "host" > environment that contains a "sysroot". The sysroot is a set of target > libraries and headers files that are used to generate packages for a > non-x86 Linux system. So, I have an environment that gets built up > over time as packages state their requirements. Since a clean of the > chroot would blow away my sysroot, I don't want that to happen and go > to great pains to insure that all the config files default 'clean' to > false and all command lines have --no-clean. I suppose I could copy > the sysroot out after the build and back in before a new build, but > that just seems hokey... so is there something WRONG with --no-clean? Does that not meet your requirements? -sv -- Fedora-buildsys-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
