On Tue, Oct 25, 2016 at 6:35 AM, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
> On Tue, Oct 25, 2016 at 09:14:14AM +0200, Vít Ondruch wrote:
>> 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
>
> The problem with this is the first time there is a mass rebuild, or a
> packager uses rpmdev-bumpspec, or we just have a naive packager who
> doesn't understand what's happening, you'll end up with:
>
> %changelog
> * Fri Oct 21 2016 Some One <someone@xxxxxxxxxxx> - 2.3.1-59
> - Mass rebuild.
> %include %{SOURCE100}
>
> which will cause all sorts of problems (changelog will likely be out
> of order for a start).
>
> I agree with the sentiment but I don't think this will work. It has
> to be coordinated across the whole distro and tooling.
>
> SUSE deleted all their RPM changelogs a very long time ago, we should
> do the same.
>
> Rich.
It would probably be better if %changelog grew a "-f" flag so that you
can point it to a file instead of using %include. It's also idiomatic
(we do this for %files lists, too).
That behavior could also allow for truncating to the most recent
entries in the spec itself, while keeping the rest in a changes file
that gets appended to the end of the in-spec changelog. Of course, if
there's no entries, then only the changes file would be merged into
the spec.
--
真実はいつも一つ！/ Always, there's only one truth!
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
