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.
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.
Note above; we are not "enforcing interactiveness." Originally ebuilds
were not supposed to be interactive; I would say it is still frowned
upon by many people. However we have to accept that interactivity is
required in certain instances and this metadata allows people to ignore
these ebuilds when doing things like automated ebuild testing...unless
the games team wants to donate all the media for their games ;)
As for the GLEP itself; I'd like to see some patches, particularly for
the resolver to show the restriction up front. Also a patch to the
ebuild.5 manpage for RESTRICT=interactive prior to seeing the glep get
approved.
--
[email protected] mailing list
