On Fri, Nov 08, 2019 at 03:48:36PM +0100, Dominique Leuenberger / DimStar wrote:
I assume: maxnum = 0 means no cutting based on count of changelog entries, only on the date cuttime: the same as _changelog_trimtime would be doing minnum: how manu changes entries to keep, beyond even if going beyont the cuttime (so basically what Bernhard's _changelog_mincount would be doing.
Yes, setting a component to 0 disables it.
So, as you asked so nicely:
why on earth is that a suse specific patch and not upstreamed? (yeah, I can use the same polemic)
Why do you ask me? Rpm upstream knows about this patch. We can retry to get it upstream, though.
and why on earth is that not documented anywhere? even googling for %_binarychangelogtrim (when one already knows about it) yields just three results (dups filtered by google)
It has the same documentation level as %_changelog_trimtime ;-) How did you stumble over that macro?
So, please, work with upstream to get such stuff upstreamed and eliminate downstream patches.
We aleady do that. (Surprise, surprise) Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org