Some packagers also create a new file with older changelog entries (e.g. vim). And yes SPEC files can indeed get quite bloated with too many changelog entries and it would be nice if there was a set rule or guideline on how to deal with that. Regards, Charalampos Stratakis Associate Software Engineer Python Maintenance Team, Red Hat ----- Original Message ----- From: "Michael Catanzaro" <mcatanzaro@xxxxxxxxx> To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> Sent: Sunday, October 23, 2016 4:09:35 PM Subject: RPM %changelog? On Sun, 2016-10-23 at 03:49 +0000, Christopher wrote: > 2. Should I preserve the entire changelog in the SPEC? Or should I > roll it > over when I update to the latest upstream? It seems the changelog > could > easily become the bulk of a package if everything is preserved, and > I'd > think git would suffice for anything older than the last few rebases > onto > latest upstream. This is indeed annoying. In most packages, the changelog is almost the entire spec file. Some packagers eventually delete old changelog entries, most don't. SUSE has a %changelog RPM macro that fixes this by moving the changelog into a .changes file stored in the same directory. Every SUSE package uses it. Probably we should too? Michael _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
