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]

 



Dne 25. 02. 20 v 15:03 Pierre-Yves Chibon napsal(a):
> On Tue, Feb 25, 2020 at 12:59:39PM +0100, Vít Ondruch wrote:
>
> [About the release field]
>
>> I am not really sure about this. How do you envision this is going to be
>> implemented? Is there going to be "release" file, similarly to
>> changelog, which would help me to override this?


I just wanted to stress out that I believe it would be good idea to use
similar approach for changelog as well as for release. I.e. both should
be opt-in, stored externally, overridable, and the automation should
kick in only if they were not touched by the last commit.


Vít


>>  Because, currently, it
>> seems that both methods are going to need a lot of information from the
>> build system. 
> The first method using number of commits and number of builds, pull limited
> information from the build system (just: how many builds succeed before this one
> with this version and release?).
> The second method does rely heavily on the build system.
>
>> They will need to parse .spec file etc. I don't see this
>> to be able to handle even a bit more complex stuff like e.g.
>> https://src.fedoraproject.org/rpms/ruby/blob/master/f/ruby.spec#_26
> We've been trying to find something that fit the majority of the packages but we
> are well aware that there are and will always be some special snowflakes that
> will not be able to adhere to this.
> I'd be happy if this works makes life/packaging easier for 50% of our packages
> (I'd even probably be happy if it's 20%).
> Once we have the simple case out and we can test it, see how it behaves, what
> its limits are, we can start building on more complex cases, but I don't really
> believe on building the perfect solution in one go.
>
>
> Pierre
> _______________________________________________
> 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