So why don't we optionally split changelog out of the .spec file?
Something like this might be first step:
$ sed -n '/^*/,$ p' ruby.spec > ruby.changes
$ git diff
diff --git a/ruby.spec b/ruby.spec
index 2817201..c82740d 100644
--- a/ruby.spec
+++ b/ruby.spec
@@ -92,6 +92,7 @@ Source10: rubygems.prov
Source12: test_abrt.rb
# SystemTap tests.
Source13: test_systemtap.rb
+Source100: ruby.changes
# The load directive is supported since RPM 4.12, i.e. F21+. The build
process
# fails on older Fedoras.
@@ -971,1212 +972,4 @@ make check TESTS="-v $DISABLE_TESTS"
%{ruby_libdir}/tkextlib
%changelog
-* Fri Oct 21 2016 Vít Ondruch <vondruch@xxxxxxxxxx> - 2.3.1-59
-- Continue to use OpenSSL 1.0 for the moment.
-- Add gemspec_add_dep and gemspec_remove_dep macros.
-- Harden package.
-
... snip ...
-
-* Mon Mar 9 1998 Shoichi OZAWA <shoch@xxxxxxxxxx>
-- Added a powerPC arch part. Thanks, MURATA Nobuhiro
<nob@xxxxxxxxxxxxxxxxxxx>
+%include %{SOURCE100}
This would produce precisely the same output, while it can be edited
manually or regenerated by scrip if one wishes.
Vít
Dne 23.10.2016 v 16:09 Michael Catanzaro napsal(a):
> 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
