Re: Packages which use the BuildRoot: directive

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

 



On 12.7.2018 00:11, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jul 11, 2018 at 12:47:40PM -0700, Kevin Fenzi wrote:
The guidelines currently say:

https://fedoraproject.org/wiki/Packaging:Guidelines#Spec_Maintenance_and_Canonicity

"Fedora's git repository is the canonical location for Fedora spec
files. Maintainers MUST expect that other maintainers and automated
tooling will make changes to their packages, potentially without
communicating prior to doing so (though communication is always
encouraged). If some maintainers are also attempting to keep copies of a
spec in an outside repository, they MUST be prepared to merge changes
made to the spec in Fedora's repository, and MUST NOT overwrite those
changes with a copy from an external repository or using fedpkg import."

I think this guideline is bad and counterproduuctive, since many
packages clearly ignore it.
It would be "counterproductive" if it increased the occurrence of the
unwanted thing. If it's sometimes ignored, sometimes not, it's not
counterproductive, but maybe not as effective as (some) would like.

So what do we do? Take the package away from
(most likely) upstream developers? Tell them no no no very sternly so
they can ignore us?
Actually I think this setup is more often used by projects that are
Fedora-only or RHEL-and-Fedora-only, than fully independent upstream
projects. So we do have leverage.

I second that. When we mass filled PRs with python2 related changes it was always a Red Hat maintained software, where people were basically telling us: "no, we won't accept your PR here, we maintain the specfile somewhere else". It was very unpleasant experience and usually such maintainers expects us to:

1) find their canonical spec file location and figure out what special branch we need to apply the patch to

2) wait for a new release of their software to happen and specfile changes be "backported" into Fedora (sometimes took months)

Some maintainers were kinder than others, taking the changes and applying them in their god-knows-where mainained spec files. Some where not.

We don't need to make the rule less strict, we need to find a way to enforce it. The current state (people ignoring this rule) makes contributing to Fedora even harder than it already is.

--
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/CAAVYJILILR2VJKUJXTL64CK6BI3UNIW/




[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