On Fri, Jan 10, 2020 at 05:36:46PM +0100, Pierre-Yves Chibon wrote: > > The release field would need to be set by koji ignoring whatever is in the > spec file. How do we want to do this? > - Based on dates? > - Using an always increasing integer? > - Using the number of successful builds since the last time the version > field changed? > - Another idea? > Obsoletes RPM tag is usually specific up to release value. Therefore the new release scheme must hold two properties: (1) The value must be predictable. I.e. a packager must know what release the pacakge will be assigned before commiting a change with the Obsoletes tag. (2) The new values must be larger than all historical values (across all historical Fedora releases). That assures than a new build won't become obsoleted because of a decreased release. -- Petr
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
