So what variant configs are out there? If there's a ton, then I agree we
should focus on the core configurations and let people that have their own
setups provide a separate package. I guess the mock-configs.src.rpm could
generate sub-packages: mock-core-configs (e.g. Fedora), and possibly
mock-configs-centos?
On Wed, Sep 6, 2017 at 2:57 PM John Florian <john(a)doubledog.org> wrote:
On Wed, 2017-09-06 at 12:08 -0400, John Florian wrote:
On Wed, 2017-09-06 at 15:04 +0200, Miroslav Suchý wrote:
I would like to split mock package into two separate packages: mock and mock-config. I
mean even sources, so we will
have two src.rpm packages.
Mock-config will have all chroot configs. Basically anything in /etc/mock* but
site-defaults.cfg.
This change will allow immediate update of configs when Fedora is branched.
Any comments?
I like the idea of having these split if for no other reason than to
compartmentalize the changelogs into two nice logical sets.
Also +1 for the mock-fedora naming suggested by Sérgio. That sets a
nice prominent example for others to follow and is very admin friendly
if one wound up with several of these somehow.
Actually, I like Neal's naming suggestion better (mock-core-configs). I
was thinking it was Fedora-only, but that's clearly incorrect.
_______________________________________________
buildsys mailing list -- buildsys(a)lists.fedoraproject.org
To unsubscribe send an email to buildsys-leave(a)lists.fedoraproject.org
--
The United States Coast Guard:
Ruining natural selection since 1790