Re: Defining the future of the packager workflow in Fedora

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

 



Fabio Valentini wrote:
> Additionally, if-guarding every non-backwards compatible change will
> result in unmaintainable, brittle and broken .spec files pretty fast.
> Nobody should be expected to work through if-else-endif spaghetti (and I'm
> not even talking about automated tools here, which almost never will
> handle conditionals entirely correctly, and probably never can). And never
> mind that people don't actually remove conditionals for EOL fedora
> releases ...

I do, for most packages. At least when I need to work on the package anyway. 
I wouldn't submit a build just for that.

Though for some packages, I get told to leave ancient conditionals in for 
EPEL. (You can usually recognize them because the conditionals also include 
%{?rhel}.)

        Kevin Kofler
_______________________________________________
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