We have reached a sufficiently large number of gap-pkg-<foo> packages that guidelines seem like a good idea. Initial draft here:
I regret that I will not be available to answer questions during the meeting. I will be discussing my daughter's braces with an orthodontist at that time. Something tells me that discussing GAP packaging guidelines would be a less expensive endeavor.
We discussed this at this weeks meeting (http://meetbot.fedoraproject.org/fedora-meeting-1/2016-05-19/fpc.2016-05-19-16.00.txt):
Very cool ideas. The example should not be hard to generate. I'll work on that today.
As for the weak deps, I don't see how a single choice can be right for all packages. I have already mapped some to Recommends and some to Suggests in the existing gap-pkg-foo packages, based on reading the documentation to determine just how weak the weak dep is. Unfortunately, that also makes an auto dep generator problematic, as cool as that would be.
The cruft-cleaning macro is a good idea. I'll whip one up today.
I have written the proposal into the main guidelines. I'm not sure what happened with that example or anti-cruft macro, so I'll drop this back to needinfo after I've made the announcement.
I've also added the appropriate references in the main and naming pages.
A set of guidelines for GAP packages has been added.
Metadata Update from @james:
- Issue assigned to tibbs
to comment on this ticket.