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
x11-base/xcb-proto: Install 1.14 for the correct Python versions #15143
Conversation
On my system, I had 3.7 and 3.8 selected but it was installing for 2.7, even though that's not one of the targets! 2.7 had accidentally become my eselected Python. configure was picking this up, detecting the sitedir, and locking it into the Makefile, preventing python_foreach_impl from having any effect. It is simpler and safer to override the Makefile's pythondir with the sitedir value returned by the eclass. Package-Manager: Portage-2.3.96, Repoman-2.3.20 Signed-off-by: James Le Cuirot <chewi@gentoo.org>
Pull Request assignmentSubmitter: @chewi x11-base/xcb-proto: @gentoo/x11 Linked bugsNo bugs to link found. If your pull request references any of the Gentoo bug reports, please add appropriate GLEP 66 tags to the commit message and request reassignment. If you do not receive any reply to this pull request, please open or link a bug to attract the attention of maintainers. In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
Thanks! |
On my system, I had 3.7 and 3.8 selected but it was installing for
2.7, even though that's not one of the targets! 2.7 had accidentally
become my eselected Python. configure was picking this up, detecting
the sitedir, and locking it into the Makefile, preventing
python_foreach_impl from having any effect. It is simpler and safer to
override the Makefile's pythondir with the sitedir value returned by
the eclass.
Package-Manager: Portage-2.3.96, Repoman-2.3.20
Signed-off-by: James Le Cuirot chewi@gentoo.org