Hi list, Stephen John Smoogen <smooge@xxxxxxxxx> writes: > On Mon, 24 Feb 2020 at 11:50, Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> > wrote: > >> Good Morning Everyone, >> >> This topic has already been discussed a few times over the past month, but >> Adam >> Saleh, Nils Philippsen and myself have had the opportunity to invest some >> time >> on it with the hope of making the packager's life simpler as well as >> making it >> easier to build automation around our package maintenance. >> > > > Going through the various discussions, I think we are running into a > classic sausage factory problem.. everyone wants to have their favourite > meat, but the only way to make it work is mix them all together, grind it > up and come up with something else. I have to agree with Stephen here. As someone who has been heavily involved in building packages on OBS, where the Release field is generated automatically by the build server: I don't see a problem in automatically generating the release field, I would actually very much welcome it. But then none of my packages fall into the "Beaufort D'Ete" category, so I might be missing something here. For the changelog: yes please, generate it from the commit log! They are more or less the same for all my packages and I'm getting tired of copy pasting the same text into %changelog and git commit. Cheers, Dan
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
