On Sun, Oct 23, 2016 at 10:39 AM, Peter Robinson <pbrobinson@xxxxxxxxx> wrote: > On Sun, Oct 23, 2016 at 3:09 PM, Michael Catanzaro <mcatanzaro@xxxxxxxxx> wrote: >> 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? > > There's also an option which trims the installed size to a max amount > (not sure what it is off hand) which is probably useful, not sure what > a changes file provides over say a git change log for the package, is > it shipped in the rpm, or is it just for reference? SUSE's Open Build Service runs a source service that converts the changes data to a changelog and appends it to the spec at the time of building the package. The service is called changelog2spec[1] and it's part of obs-build. Some packagers also ship the changes file as a doc in the RPM itself, but that's increasingly rare. [1]: https://github.com/openSUSE/obs-build/blob/master/changelog2spec -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
