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]

 



On Thu, 27 Feb 2020 at 10:47, Nicolas Mailhot via devel
<devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Le 2020-02-27 09:52, Miro Hrončok a écrit :
> > On 27. 02. 20 9:20, Pierre-Yves Chibon wrote:
> >>> How would that work with "complex" releases? For example release
> >>> containing
> >>> prerelease info like 0.1.beta.2 or 0.1.20120225gitd6c789a? Many Go
> >>> package
> >>> have no version, so depend heavily on the Release tag to signal what
> >>> is the
> >>> snapshot date and git commit packaged.
> >> This is something that we will need to investigate and clarify a
> >> little more,
> >> the answer may very well be: it won't, but let's investigate this
> >> first.
> >
> > There are three ways of of there I can think of ATM:
> >
> >  1. (as said by Pierre) make it opt-in only and don't handle this
> >  2. (as said by Neal) don't do this, use 0.1~beta.2-<release>
> >  3. allow to keep the Release filed if it uses %{baserelease}
> >
> > %{baserelease} is already respected by rpmdev-bumpspec (and hence mass
> > rebuilds)
> >
> >
> >   %global baserelease 8
> >   Release:
> > iamcrazy1234568andIknowit.%{baserelease}.whatnot~foo666%{?dist}
> >
> > bumpspec does:
> >
> >   %global baserelease 9
> >   Release:
> > iamcrazy1234568andIknowit.%{baserelease}.whatnot~foo666%{?dist}
>
> Go (and other) packages do not set Version nor Release. They set
> distprefixNUMBER, which is defined in
> https://src.fedoraproject.org/rpms/fedora-release/blob/master/f/fedora-release.spec#_488

Hello Nicolas,

can you, please, show an example of such package? I was searching through some
golang packages because I was curious how it works but couldn't find
an example (i.e. those packages had Version
and Release set, e.g.
https://src.fedoraproject.org/rpms/golang-github-anacrolix-missinggo/blob/master/f/golang-github-anacrolix-missinggo.spec).

>
> This automation must be kept or migrated to something else if people do
> not want to keep it ("just write bogus upstream versions manually is not
> a forward path)
>
> If changelog is automated, distprefixNUMBER should end up somewhere in
> it, because that’s important information not present in Version
>
> https://src.fedoraproject.org/rpms/fedora-release/blob/master/f/fedora-release.spec#_488
> also defines some things equivalent to a distpostfix. They probably
> belong in changelog too.
>
> 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
_______________________________________________
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