Re: Ideas and proposal for removing changelog and release fields from spec file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le mercredi 26 février 2020 à 23:07 -0500, Neal Gompa a écrit :
> 
> You don't use Release for upstream versioning, even for snapshots.
> For
> your examples:
> 
> * 0-0.1.beta.2 -> 0~beta.2-1
> * 0-0.1.20120225gitd6c789a -> 0~git20120225.d6c789a-

Sorry but no

You are attempting to redefine the meaning of Version (*upstream*
version) to accomodate your release simplification plans

As I wrote the list months ago the upstream Version (Version,
%{version}) is zero 0 nil not 0~git20120225.d6c789a-1

The git20120225.d6c789a is a Fedora downstream construct

You can not break the data model with automation the way you break it
for humans. Automation does not care about your feelings. Automation
input is O as upstream Version. It can add downstream constructs to
Release, it can not rewrite Version (bad bad idea to attempt rewriting
a core rpm Tag in macros anyway)


-- 
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux