Hello,
today at Nest, somebody said "unfortunately, there is no way to tell what package to install to get a particular RPM macro".
I think that having an RPM provides generator for "rpm-macro(__python3)" or similar should be a fairly simple exercise.
Would you folks consider that useful?
I think that would be very helpful!
Cheers,
Dan
On August 6, 2021 6:55:00 PM UTC, "Miro Hrončok" mhroncok@redhat.com wrote:
Hello,
today at Nest, somebody said "unfortunately, there is no way to tell what package to install to get a particular RPM macro".
I think that having an RPM provides generator for "rpm-macro(__python3)" or similar should be a fairly simple exercise.
Would you folks consider that useful?
On Sat, 7 Aug 2021, 07:26 Dan Čermák, dan.cermak@cgc-instruments.de wrote:
I think that would be very helpful!
Cheers,
Dan
On August 6, 2021 6:55:00 PM UTC, "Miro Hrončok" mhroncok@redhat.com wrote:
Hello,
today at Nest, somebody said "unfortunately, there is no way to tell what package to install to get a particular RPM macro".
I think that having an RPM provides generator for "rpm-macro(__python3)"
or
similar should be a fairly simple exercise.
Would you folks consider that useful?
Would be useful, I have often found myself greping the macros to work out which file and package a macro is in.
The follow up is to auto-generate the BuildRequires. Probably no mechanism exists.
packaging mailing list -- packaging@lists.fedoraproject.org To unsubscribe send an email to packaging-leave@lists.fedoraproject.org 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/packaging@lists.fedoraproject.... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
V Fri, Aug 06, 2021 at 08:55:00PM +0200, Miro Hrončok napsal(a):
today at Nest, somebody said "unfortunately, there is no way to tell what package to install to get a particular RPM macro".
I think that having an RPM provides generator for "rpm-macro(__python3)" or similar should be a fairly simple exercise.
Would you folks consider that useful?
Definitely.
-- Petr
On 06. 08. 21 20:55, Miro Hrončok wrote:
Hello,
today at Nest, somebody said "unfortunately, there is no way to tell what package to install to get a particular RPM macro".
I think that having an RPM provides generator for "rpm-macro(__python3)" or similar should be a fairly simple exercise.
Would you folks consider that useful?
For the record, this landed in Fedora 37+:
https://github.com/rpm-software-management/rpm/pull/1758
$ repoquery -q --repo=fedora --releasever=37 --provides python-srpm-macros ... rpm_macro(_python_bytecompile_errors_terminate_build) rpm_macro(_python_bytecompile_extra) rpm_macro(py2_dist) rpm_macro(py3_dist) rpm_macro(py_auto_byte_compile) rpm_macro(py_dist_name) rpm_macro(py_provides) rpm_macro(pypi_source) rpm_macro(python) rpm_macro(python2) rpm_macro(python3) rpm_macro(python3_pkgversion) rpm_macro(python_extras_subpkg) rpm_macro(python_wheel_dir) rpm_macro(python_wheel_pkg_prefix)
$ repoquery -q --repo=fedora --releasever=37 --provides pyproject-rpm-macros ... rpm_macro(_pyproject_builddir) rpm_macro(_pyproject_files_prefix) rpm_macro(_pyproject_ghost_distinfo) rpm_macro(_pyproject_modules) rpm_macro(_pyproject_record) rpm_macro(_pyproject_wheeldir) rpm_macro(_set_pytest_addopts) rpm_macro(default_toxenv) rpm_macro(pyproject_build_lib) rpm_macro(pyproject_buildrequires) rpm_macro(pyproject_check_import) rpm_macro(pyproject_extras_subpkg) rpm_macro(pyproject_files) rpm_macro(pyproject_install) rpm_macro(pyproject_save_files) rpm_macro(pyproject_wheel) rpm_macro(tox) rpm_macro(toxenv)
Thanks, Dan.
packaging@lists.fedoraproject.org
-
Dan Čermák -
Miro Hrončok -
Petr Pisar -
Steve Traylen