On 7/7/07, Steve Long <[EMAIL PROTECTED]> wrote:
I'm ofc not including fetch-restricted which also require interaction, although that is standardised enough for a script to deal with[1]. Having found this for games, I can deal with that too ofc, but I still think the
I'm not sure whether special license agreements are a legitimate case for interactivity in some ebuilds, but I can tell you the einput eclass was intended to be used only in pkg_config(), meaning the only time the user would ever encounter einput is when they specifically run "emerge --config foo" after installation, and even then it would be only in a handful of ebuilds that actually need einput's services. Burdening the user with the prospect of interactivity in any other ebuild phase does seem to go against the Portage philosophy, so I feel that einput.eclass is an edge case tool at best. -- [EMAIL PROTECTED] mailing list
