On Thu, Jan 22, 2015 at 03:15:48PM +0100, Miroslav Suchý wrote:
I just spoke with two members of DNF team about default usage of DNF
in mock. I would like to share outcomes of this
meeting.
First I would like to state that you can already optionally use DNF in your mock by
setting:
config_opts['package_manager'] = 'dnf'
in your
/etc/mock/site-defaults.cfg
It is present in mock for half a year and all known problems have
been resolved for some time.
I've been using dnf in mock. It mostly works
nicely, and the nosync
plugin is a killer feature for me, it makes mock builds almost as fast
as 'fedpkg local'. I encounter a bug though where
/tmp/<something>/lib/nosync.so
is reported linked into compiled binaries (#1184964), but it appears to be
just a cosmetic issue.
Maybe you should consider turning nosync on too?
You can even set this option per chroot target. E.g. put this line
only in
/etc/mock/fedora-rawhide-x86_64.cfg
and then only rawhide-x86_64 builds will use dnf while everything else will use yum.
DNF should be default packager manager in Fedora 22, so I started thinking how it affects
mock.
I have a notion, that after branching of Fedora 22 I will change
/etc/mock/fedora-rawhide-*.cfg
to use DNF by default. I.e. everything build for Fedora 23 would use
DNF for building.
I think that is reasonable.
Zbyszek