> How are version numbers handed upstream?
Upstream did choose a version, but the releases are rather infrequent,
so I'd prefer to use snapshots.
> Would a simple date work for you?
>
> Source1: url-of-branch-1-source
> Source2: url-of-branch-2-source
> ...
>
> Version: 0
> Release: 1.20210329%{?dist}
This could work, but it has a slightly different pitfall -
while rpmdev-bumpspec does properly update the Release: tag
on the subpackages, it does not modify the Requires:,
again rending them unsatisfiable.
In both cases (i.e. your suggestion and my idea) this isn't
a large problem - fixing it would take a minute or two -
but it still means having to do some extra work whenever
Mass Rebuild comes along and all the specs get automatically bumped.
_______________________________________________
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
