Learn more about these different git repos.
Other Git URLs
The EPEL sig has decided to revamp playground and as part of that we want it to be opt-in, not required for epel8 branches.
So there is no longer any need to support package.cfg. At the minimum the warning if an epel* branch does not contain a package.cfg file should be removed, but support for that file should probably be removed altogether.
package.cfg
See also #414.
@salimma I don't have complaints against complete removal of package.cfg support from rpkg. I am even glad to do this. But before the removal, I would like to make sure. You say "there is no longer any need to support". What about packagers who would like to opt-in and build both epel8 releases together the old way? Yes, they can execute build twice (once for epel8 and once for playground) without the current support. Using package.cfg is currently optional. Warnings can be removed, support can stay. Or do I understand it wrong?
otherwise, package.cfg support seems like a big chunk of code: https://pagure.io/fedpkg/c/bcbb337e5076f8edad332067a64b7d4e6da279b6?branch=master
Commit 781036e fixes this issue
Metadata Update from @onosek: - Issue set to the milestone: 1.40
Login to comment on this ticket.