Re: F43 Change Proposal: Deprecate RPM Macros for setup.py-based Python Builds (self-contained)

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

 



On 18. 06. 25 22:22, Michael J Gruber wrote:
This example and most that I know use a BR on python3-devel and
%pyproject_buildrequires, whereas the guidelines tell you to use *one*
of them. The result with both is the same as with just the macro, but
the path there is different: in the latter case the macro installs
python3-devel. I don't mind either way, but maybe we should decide on a
"best practice" and have the guidelines and examples match.
The guidelines say you MUST use at least one of them.

The best practice however, is to follow the examples in the guidelines.

---

The reason for the rule is that:

1) Not all RPM packages that need BR on python3-devel are "Python packages" to use %pyproject_* macros.

2) Packages that use the pyproject declarative BuildSystem to reduce boilerplate use %pyproject_buildrequires implicitly and gain a BR on python3-devel.


--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: 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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[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