On Sun, Apr 4, 2021 at 11:19 AM Artur Frenszek-Iwicki
<suve@xxxxxxxxxxxxxxxxx> wrote:
>
> I thought about it some more and realised that using just the date allows me to stick everything in one package. Basically, the idea is:
>
> %global branch1_date 20210101
> %global branch2_date 20210202
> %global branch3_date 20210303
>
> %global package_date %( bash scriptlet that picks max value from %{branchX_date} macros )
> Version: 2.0
> Release: %{package_date}.1%{?dist}
>
> I think this should work fine, while also not breaking the packaging guidelines. Thanks for the suggestion.
Wasn't your first problem that you want to have a Release tag that
rpmdev-bumpspec can deal with? I doubt that will be the case with this
format.
Instead, I suggest you switch the "1" (incrementing integer) part and
the %{package_date} part, which also matches the Packaging Guidelines
better, and should not confuse rpmdev-bumpspec.
Fabio
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
