Re: Trimming (or obsoleting) %changelog?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/17/2013 12:03 PM, drago01 wrote:
On Wed, Apr 17, 2013 at 5:18 AM, Mathieu Bridon
<bochecha@xxxxxxxxxxxxxxxxx> 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?
- What are the changes since "<old> NVR"?
- 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.

Ralf

--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux