On Sun, Oct 23, 2016 at 03:39:06PM +0100, Peter Robinson 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? http://pkgs.fedoraproject.org/cgit/rpms/libguestfs.git/tree/libguestfs.spec#n28 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
