-
Notifications
You must be signed in to change notification settings - Fork 993
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
Do not add architecture to system packages by default, only when cross-compiling #12349
Conversation
I don't think this closes #12320, because the situation stays the same during cross compilation: for a given recipe either:
To fix the issue, we would need to have a method which installs the system packages it receives as argument, with |
Hi @ericLemanissier, thanks for the comments. The intention of this PR is to:
Passing Thanks a lot. |
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.
Looks like a good default with the possibility of adding fine-grained control in the future 👍
Changelog: Feature: Do not add architecture to system packages by default, only when cross-compiling.
Docs: omit
The most common situation when installing system packages is that you don't use the architecture in the package name unless you are cross-compiling, so this defaults to that behaviour.
Also it's testing how to install archless packages even with cross-compilation, but that's something we probably want to change as the code would look a bit ugly. You can workaround that with an empty dictionary as arch_names in classes that accept the argument:
Closes: #12320