-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeff Sheltren wrote:
On Jul 17, 2006, at 4:57 PM, Clark Williams wrote:
>
> Now, I really don't like the idea of adding *anything* to the default
> build chroot (other than what's required to build a package). It's
> slow enough as it is and for the most common usage (plague/mock
> builds) we don't want anything except what's absolutely needed. So,
> how would we go about managing a chroot for tasks like testing? Do we
> add an 'install' command to install stuff from the configured
> repositories into the chroot, like this:
>
> $ mock install rpmlint
>
> Or do we do something else? Do we make tester's put together their own
> cfg with a modified buildsys-build rpm that includes the packages they
> need? Is there a simpler mechanism for someone that wants a chroot for
> testing?
>
> Clark
>
I've always just used yum from the host system with the
--installroot flag. You don't want to rely upon the RPM tools
inside of the chroot because those won't always work - remember, we
are doing all the package installs with the host system's yum in the
first place. My vote would be to keep mock as simple/minimal as
possible.
Ah, I hadn't thought about that. RPM and friends work fine in the FC5
chroot on my FC5 laptop, but I'm betting an FC2 chroot would yak all
over the place. :)
So someone wanting to put together a testing chroot would do something
like this:
$ mock -r fedora-5-i386-core init
$ yum --installroot=/var/lib/mock/fedora-5-i386-core/root
- --enablerepo=<my FC5 repo> install <my packages>
$ mock -r fedora-5-i386-core chroot <my test command>
I probably don't have that yum command right, but you should get my
intent. Is that the way you use it?
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org
iD8DBQFEvBcTHyuj/+TTEp0RAgN2AJ0RF1KLvomfnbA8/g/9w2sDUZm6RQCeMvnB
TxuUnKmqAkcAQJjeDCbF/iU=
=174P
-----END PGP SIGNATURE-----