On Sun, 2006-09-03 at 16:56 -0500, Clark Williams wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Jesse Keating wrote:
> On Sat, 2006-09-02 at 13:38 -0500, Clark Williams wrote:
>> 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.
> Ok, I haven't played with the 0.7, but surely you've made some space
> available to do commands like this? We depend heavily on being able to
> install a package or package list in the buildroot then run some
> commands in the buildroot. Its an integral part of our tree composition
The 'chroot' command for running commands in the build root is still
there, so you can run whatever you need in the chroot. What remains is
to make it easy to install arbitrary rpms into the chroot. I think the
way to do this is to have an 'install' command that accepts binary rpms
(i.e. doesn't involve yum repositories) and runs the host rpm to put the
contents into the build root.
Hmmm. Thinking about this a bit more makes me wonder if we need to be
able to install rpm's *using* yum, since yum brings with it the ability
to resolve dependencies. I say this because the RPM we just generated
with mock might have Requires: that aren't in the build chroot and would
need to be there for installing the the rpm prior to running rpmlint. I
hate to add one command to install a local rpm and another to install
using yum. A quick scan of the yum man page makes me think that it might
work to just invoke 'yum install <path to rpm>'.
Can anyone confirm/deny that invoking yum with a path to an rpm will
work (I'm not in a position to do so at the moment).
yes, it works. You might want to check where it expects to find the rpm
when using an installroot ie: does it find it in /path/to/rpm or
I don't remember which at this moment.