Trimming (or obsoleting) %changelog?

[Ralf Corsepius]

On 04/17/2013 12:19 PM, drago01 wrote:
> On Wed, Apr 17, 2013 at 12:11 PM, Ralf Corsepius <rc040203 at freenet.de> wrote:
>> On 04/17/2013 12:03 PM, drago01 wrote:
>>>
>>> On Wed, Apr 17, 2013 at 5:18 AM, Mathieu Bridon
>>> <bochecha at fedoraproject.org> wrote:
>>>>
>>>> On Wed, 2013-04-17 at 12:10 +0900, Florian Festi wrote:
>>>>>
>>>>> For limiting the change log entries in the binary packages
>>>>> %_changelog_trimtime can be used that take a unix time stamp as an
>>>>> integer value. This way the whole history is still available in the spec
>>>>> file.
>>>>
>>>>
>>>> Could redhat-rpm-config set that automatically, for example to the
>>>> release date of Fedora N-1?
>>>
>>>
>>> Why does it have to be date based?
>>> Why not having a count based cutoff?
>>> Like last N entries.
>>
>> Ask yourself what changelogs are serve for and you'll find the answer.
>>
>> It's questions such as:
>> - When did a change make it into a package?
>
> This is available in the git repo.

Jesus Christ - The git repos are not available to ordinary users, nor 
are they easily accessible!


>> - What are the changes since "<old> NVR"?
>
> Same here ... you can view a log from commit to commit to view that
> (even diffs).
>
>> - Which changes are relevant to %changelog users?
>> ...
>>
>> That is, cutting at <N> would cut at points, which are likely cut off off
>> the information users are interested in.
>
>
> We are using git.
The packagers are using git - The distro's users aren't.

> You have everything there (not only the changelogs
> but the old versions of spec file / patches).

That's an urban myth.

Ralf