Alec Warner wrote: >>>> Title: RESTRICT=interactive >>> I'd say it's good idea, although isn't RESTRICT=interactive a slight >>> misnomer? You are enforcing interactiveness, not restricting it :) >>> Although RESTRICT="non-interactive" sounds weird too, and introducing >>> new variable would be bloating. > > If you look at every other RESTRICT match you will find they follow a > similar "backwards" pattern.
No, all the other ones make sense when you read them as "restrict
(disallow) $foo-ing."
> RESTRICT="fetch" -> turns off fetching
> RESTRICT="strip" -> don't strip binaries
> RESTRICT="test" -> Don't call pkg_test
> RESTRICT="interactive" -> This ebuild is interactive.
>
> If you read it like you are placing a specific restriction:
> "A {test,strip,fetch,interactive} restriction on the ebuild"
> then the naming scheme makes a bit more sense.
It still doesn't make sense. Restricting any other feature disallows it.
Restricting interaction allows it. Find a word that's the antonym of
interactive, and restrict that.
This isn't a huge issue in the scope of the GLEP, but it is one that
needs to get fixed.
Thanks,
Donnie
signature.asc
Description: OpenPGP digital signature
