time to implement a 'yum' object in mock?

[Ville Skyttä]

On Monday 13 December 2010, seth vidal wrote:
> On Mon, 2010-12-13 at 09:48 -0600, Clark Williams wrote:
> > The reason I am pondering directly accessing yum is that currently we
> > parse the output of the resolvedep command and string processing is
> > notoriously fragile once you leave the C locale. If we just make calls
> > into yum and get back objects representing the missing dependencies
> > (rather than parsing yum output as we do now) we side-step all the
> > locale issues.
> 
> it gets rid of MOST locale issues - but it hands you more of the bizarro
> unicode issues :(. I would recommend making sure you enforce locale=C if
> you're going to use yum as a module to minimize unicodedecode
> tracebacks.
> 
> The other thing that might be worth considering is using yum as an cli
> interface for the install/update calls but use the api for resolvedep.

Note that current mock git (and 1.1.7 I gather) only use resolvedep for the 
more_buildreqs stuff from configs, which I guess is a quite rarely used 
feature.  Regular build dependencies are now installed with yum-builddep.