New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build/ops: rpm: Python 3-only ceph-disk and ceph-volume #20140
Conversation
10d6913
to
13dd460
Compare
%{python_sitelib}/ceph_detect_init* | ||
%{python_sitelib}/ceph_disk* | ||
%else | ||
%{python3_sitelib}/ceph_detect_init* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it possible to use %{python%{_python_buildid}_sitelib} ? i.e macro in macro name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, I believe it is possible, and I see where you're going with that question - it would allow us to eliminate the conditional in this case, but if you look at how %{python_sitelib}
and %{python3_sitelib}
are conditionalized elsewhere in the spec file, it wouldn't be consistent.
In other words, we could do this near the top of the spec file: %global _python_sitelib %{python%{_python_buildid}_sitelib}
and then replace %python_sitelib
and %python3_sitelib
with %_python_sitelib
. And that would allow us to get rid of the ceph_disk and ceph_volume conditionals, but none of the others - e.g. https://github.com/ceph/ceph/blob/master/ceph.spec.in#L1160-L1168
I'd rather keep the usage consistent throughout the spec file.
da53997
to
d01d69e
Compare
jenkins test ceph-volume lvm all |
jenkins test ceph-volume tox |
Follow-up PR to #20018