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
Add and use meson-multilib.eclass #20986
Conversation
Pull Request assignmentSubmitter: @mattst88 @gentoo/github: Too many disjoint maintainers, disabling auto-assignment. 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 |
Pull request CI reportReport generated at: 2021-05-25 19:14 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
a9f76c1
to
7051d38
Compare
Pull request CI reportReport generated at: 2021-05-28 04:14 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Pull request CI reportReport generated at: 2021-05-28 04:24 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Yeah, I think "native" already conveys the multilib-nature of the functions.
I like the idea of including the output type in the function name. |
Removed Also added a patch to Still need eclass documentation for |
Pull request CI reportReport generated at: 2021-05-31 23:49 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
meson-multilib.eclass documentation completed. I've sent the two eclass patches at the beginning of the series to gentoo-dev@ for review. |
Pull request CI reportReport generated at: 2021-06-02 01:44 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Pull request CI reportReport generated at: 2021-06-02 02:14 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Pull request CI reportReport generated at: 2021-06-03 04:44 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Found and replaced a few more Planning to push this tomorrow if there are no further comments. |
Pull request CI reportReport generated at: 2021-06-03 04:59 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
414d25c
to
4c6fc4c
Compare
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Signed-off-by: Matt Turner <mattst88@gentoo.org>
There are a lot of private (i.e. to individual ebuilds and/or packages) functions implementing the necessary
meson_use
/meson_feature
-style functions for multilib.This PR factors those out and shows how we can use them in existing packages.
Consider this an RFC. I'm open to all feedback and I don't feel strongly about anything I've written here.
A couple of unorganized thoughts:
I feel like the function names are too long. Should we remove
multilib_
from the names?Trying to make the function names match
meson_use
/meson_feature
exposes the fact that themeson_use
name is weird. We want functions for the different meson options:feature
(enabled/disabled)bool
(true/false)combo
configuration).Within those, we want multilib functions that operate with and without a USE flag. One natural way to name those functions differently is to put
_use
in the name of the ones that take a USE flag, e.g., could be something likemeson_multilib_native_use_enable
vsmeson_multilib_native_enable
. But if we already are using_use
in a name likemeson_multilib_native_use
then adding another_use
is kind of nonsensical. It's for that reason that I instead havemeson_multilib_native_use
andmeson_multilib_native_true
. Perhaps we should consider deprecatingmeson_use
and replacing it with ameson_bool
? 🤷