Artur Frenszek-Iwicki kirjoitti 28.3.2021 klo 19.16:
I'm looking to package some GTK themes. Those themes come in several colour
variants. The author decided on a workflow where, instead of keeping variants
alongside each other in the tree, each variant has its own git branch.
When working with git snapshots, the packaging guidelines [1] say to put
the snapshot data in the Release: field. This is simple enough when working
with a single "main" source, but what when there's multiple sources?
How are version numbers handed upstream? Does each branch have its own
version number, all of them have the same version number, or no version
numbers are assigned at all? Assuming the last, then "Upstream has never
chosen a version" [1] would apply and package Version would be 0.
Regarding the snapinfo part of Release, the guidelines do not actually
require including commit ids for snapshots. Only date string is mandatory:
"All snapshots MUST contain a snapshot information field (<snapinfo>:)
in the Release: tag. That field must at minimum consist of the date in
eight-digit YYYYMMDD format. The packager MAY include up to 17
characters of additional information after the date."
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}
[1]:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_upstream_has_never_chosen_a_version
_______________________________________________
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
