Le 2020-02-25 10:24, Pierre-Yves Chibon a écrit :
If you make the build system provide the ${dirty_appendix} and drop the
${pivot}
(because we want to generate the release, so there is no input
specified), you
get very close to what we described.
BTW, regardless of how things up, we have existing logic that computes
dist prefixes (unpstream git commit numbers…) and appendixes
(bootstrap…).
The easy way to do things is to let things as they stand today and limit
the automation to the main release number, but that still requires
adding those things to changelog entries (if we want to trace them in
changelogs; we probably want because a project that does not releases
will be stuck at version 0 forever, only the distprefix disambiguates
what version 0 means)
OTOH, if people feel ambitious, and want to reexamine all the dist
prefix/appendix logic, there is quite a lot of work to audit the
hundreds of packages that use them today and define a migration plan and
logic. Because this amount of spec logic is not going to rewrite itself,
and expecting someone else (packagers) to do it will throw a non trivial
part of the distro under the bus.
(The correct way to do things would be to evolve rpm to have dedicated
fields for all the things we crammed into Release in the past. That’s a
non trivial endeavour.)
Regards,
--
Nicolas Mailhot
_______________________________________________
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
