On Wed, 2020-09-02 at 14:07 -0700, Kevin Fenzi wrote:
I think playground might be fixable/made of use without too much
work...
* adjust fedpkg to stop requesting playground branches always/only
request them on explicit ask
* change the inheritence in koji so it inherits from epel8
* untag all the things that are "older" in playground
* add more docs about what it is and how it works
* perhaps make it send a daily report for each compose
Whether we keep playground (but make playground inherit from epel) or
drop it entirely -- that means package.cfg is not going to be needed
either way, right?
The only one scenario I can think of where package.cfg is useful is if
someone wants their package automatically rebuilt for epel-next. But
maybe that should be done automatically the same way ELN rebuilds
Rawhide without the individual packager having to worry about it.
So... masas-retire package.cfg, perhaps?
--
Michel Alexandre Salim
profile:
https://keyoxide.org/michel@michel-slm.name
chat via email:
https://delta.chat/
GPG key: 5DCE 2E7E 9C3B 1CFF D335 C1D7 8B22 9D2F 7CCC 04F2