Dne 28.1.2017 v 07:00 Sérgio Basto napsal(a): > One thing that I have been though is about configurations, we maybe > should have a separate package with all configurations , all > files /etc/mock/*cfg except site-defaults.cfg should have separate > releases , when Fedora 27 arrive, we will need new configurations and > for that, we shouldn't release a new mock version (IMO) but a new mock- > fedora (configurations) version like RPFusion btw [1]
-1 The cadence of mock release should be faster than fedora releases. I personally target to every 2 months. So Fedora branching is always good poke to create new mock release and address all patches and reports I got in mean time. > Second thought, is use more "include statement" [2] i.e instead we > generate all /etc/mock/*cfg , maybe we can use "include statement" > for example F24 configurations is just headers and include some > templates , this could useful for example when I want change > metadata_expire=0 to metadata_expire=6h , instead need edit many files > i386, x86_64 etc I just need change in one template. +1 Patches are welcome. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys _______________________________________________ buildsys mailing list -- [email protected] To unsubscribe send an email to [email protected]
