How should mock behave when DNF is not available?

[Clark Williams]

On Wed, 11 Feb 2015 08:59:23 -0500
Josh Boyer <jwboyer at fedoraproject.org> wrote:

> On Wed, Feb 11, 2015 at 8:51 AM, Miroslav Suchy <msuchy at redhat.com> wrote:
> > I am working on switching rawhide targets to DNF. However on EL* is DNF not
> > available.
> 
> Mock isn't available on EL* either.  It's in EPEL.
> 
> > Therefore you will not be able to build rawhide packages on EL7- using
> > standard mock configuration.
> 
> Can DNF be packaged for EL7- in EPEL and used that way?
> 
> > I see several options to offer to user:
> >
> > 1) Discourage user from doing that by providing no hints how to workaround
> > it.
> >
> > 2) Tell him that DNF is not available and he must run mock with "--yum"
> > option. And warn him that he may get different depsolving.
> >
> > 3) Tell him that DNF is not available and fall back automatically to yum and
> > warn him that he may get different depsolving.
> >
> > Unless somebody will have better idea I would go with (2).
> >
> > Ideas? Comments?
> 
> If DNF can't be packaged in EPEL, then I would agree option 2 seems to
> be the best choice.

Why not #3? Seems silly to make someone restart the command when we
know that we'll need to use yum.

I'd say just shout loudly that dnf is not available, internally shift
to yum and do the build.

Clark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/buildsys/attachments/20150211/958c5499/attachment.sig>