Open thesamesam opened 2 years ago
Personally, I'd suggest using multiple inherit lines instead of extra variables for stylistic reasons. In terms of the check, I forget what exactly affects the check although I do know it doesn't handle conditionals and especially doesn't work with metadata invariance.
Personally, I'd suggest using multiple inherit lines instead of extra variables for stylistic reasons. In terms of the check, I forget what exactly affects the check although I do know it doesn't handle conditionals and especially doesn't work with metadata invariance.
Yeah, I agree. Reported in Gentoo here.
Thinking about this a bit more after @eli-schwartz pointed out an issue with meson-9999
and:
if [[ ${PV} == 9999 ]] ; then
inherit ninja-utils
else
...
fi
Couldn't we substitute things like ${PV}
with their value before passing to treesitter for parsing? ts doesn't know they're constant in the ebuild environment. (I don't think this would help the original example though.)
I suspect this is because we're not just forcing OPERA_FORCE_RPM=no, but allowing it to be overridden in the environment, which would violate metadata invariance.
opera-developer-80.0.4162.0.ebuild: