I'm just working on another ebuild with a lot of econf args, each with its own ugly '\' and relevant comments splattered randomly over the ebuild... this thing is just terrible.
Let's just mandate 'myeconfargs' in future EAPI. That is, allow doing:
# related to foo
# $(use_with baz)
I dislike the recent proliferation of magic variables that influence functions' behaviour by side effects. Passing things as explicit parameters is so much cleaner.
You could just say econf "$(myeconfargs[@]}" in the last line of your example.
I was under the impression that parameters to phase functions were strongly disliked by the Council.
econf is not a phase function.
The last line of his example is 'default', which calls a phase function.
(In reply to comment #1)
yeah, i can't see how the expansion of magic vars like this is better than accepting args to phase funcs
Let's forget about this.