On Thu, Aug 13, 2009 at 10:18:39AM +0200, J?n ONDREJ (SAL) wrote:
On Thu, Aug 13, 2009 at 09:01:51AM +0100, Richard W.M. Jones wrote:
> On Wed, Aug 12, 2009 at 04:56:15PM -0700, Jesse Keating wrote:
> > So first question, why isn't the chroot that mock created for you good
> > enough? Why do you have to create a second chroot?
>
> We have to put custom files (configuration, /init etc.) into our
> chroot, because the appliance we build is different from the host
> under which it runs. We also rm -rf large parts of the appliance in
> order to make it small enough to boot in memory.
>
> Also we don't just build in mock. In fact that is the rare case.
> Most people build using ./configure && make. And of course we support
> Debian etc.
And also there are different requirements for package build and for
appliance for libguestfs. For example mock needs gcc, ... libguestfs don't.
If there will be mock cache available in mock's chroot, then may be Rich can
use them to prefill febootstrap cache.
That's what the specfile is already doing. It is pointing febootstrap
at a yum repo populated from the mock RPM cache inside the chroot.
Daniel
--
|: Red Hat, Engineering, London -o-
http://people.redhat.com/berrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org -o-
http://ovirt.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|