Dne 29.7.2015 v 17:49 Clark Williams napsal(a):
Obviously you could fat-finger the release number and generate a
config file. Worse you might want to be using F22 but mis-type '21' and
use a wrong, but existent config. Also, I don't really like the idea of
dynamically creating files in /etc, so we might need to move the
created configs off to a /var/mock/configs directory or something like
And what about GPG keys?
[local] section in yum.conf for primary and secondary architectures differ.
And for example in case of ppc64le you could not easily substitute $arch in that Koji
Two years ago we changed mirrolist to metalink. Today we are changing yum to dnf. All this
need changes in config.
I assume that in two years the template would need some other change. So the template last
just four Fedora releases.
I think that while it is technically doable, it would lead just to confusion and IMHO the
cons will overweight the pros.
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys