Mock going forward

Clark Williams williams at redhat.com
Sat Sep 2 18:38:09 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jesse Keating wrote:
> On Sat, 2006-09-02 at 08:42 -0500, Clark Williams wrote:
>> What I haven't gotten my head around is what needs to be done for the
>> hypothetical "install" command. It may just be running yum with the
>> appropriate root arguments to install rpmlint, then just running rpm
>> to
>> install the target rpms into the chroot. Or maybe we just add rpmlint
>> to
>> the default package set. It may be that we don't need a new command
>> and
>> we can get everything done with what exists and external logic.
>>
>> I'd welcome discussion on how to do this and on how to improve chroot
>> management in general.
>>
> 
> Whats wrong with using mockhelper yum --installroot /chroot
> localinstall /path/to/buildrpms/*.rpm ?
> 

Well, because in 0.7 and greater, there is no mockhelper. The
/usr/bin/mock program is a setuid root launcher that starts "python
/usr/bin/mock.py"  with whatever arguments were passed in.

Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFE+c+RHyuj/+TTEp0RAne4AKDB6kfE7tgaa2gQXxWUw6Aac735IQCbB+8b
mwMm86+KP6wQrqzdlUdpl4w=
=Ehob
-----END PGP SIGNATURE-----




More information about the Fedora-buildsys-list mailing list