On Sun, 2010-12-12 at 10:08 -0600, Clark Williams wrote:
I was scanning BZ's for mock this weekend (yes, I occasionally do
that) and saw the one (519258) where we fail due to the fact that we're
scanning the output of yum and not correctly handling being in the
German locale. I was wondering how much code would be involved in
importing yum modules and making direct calls into the yum API?
A quick look at the code in py/mock/backend.py shows that we only call
yum with the following commands:
It's the resolvedep command that's failing, so it's possible that all
we really need to do is create a function that correctly resolves
dependencies without depending on any particular output.
Once you get the yum object setup to talk to the chroot it should be
easy to do the rest. The only question I have is if there is any selinux
reason to not have mock do it b/c of the capabilities yum is afforded?