Re: Packit-as-a-Service case studies and tips

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

 



On 08. 04. 20 12:26, Ernestas Kulik wrote:
As someone who also maintains the code for multiple packages, I say
tough luck. The workflow for keeping upstream changes buildable (and
having the ability to test the changes) and downstream package
specification in sync with said changes could not be worse currently.
Packit solves that for me*and*  gives me the ability to pull in
whatever was done downstream.

As someone who routinely does mass changes across the entire collection I appreciate you pull in whatever was done downstream. But putting the spec to upstream usually means this part is neglected.

In other words, if you are prepared to manually sync the 2 diverging spec files, feel free to keep your spec files on the Moon as far as I am concerned, but suggesting to other maintainers to maintain their Fedora spec files outside of Fedora without stressing this very important point is not helpful.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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