yes, I know about the reasons why enemy-territory have become an interactive ebuild with EULA-acception - but this is a bad solution... I started an emerge -up world and left my machine - when I came back after some hours I found that the process was not finished as expected, but was waiting for my input. A bad idea. Here's a possible solution - add some lines into the ebuild like: if [ -z "${INTERACTIVE}" ] ; then ewarn "enemy-territory needs your interaction to install please set environment variable INTERACTIVE to confirm." else ...... the actual install process ..... fi something like that. or (in case id-software would accept it that way) EULA="read_and_accepted" emerge enemy-territory and a similar ewarn like above. Reproducible: Always Steps to Reproduce: 1. 2. 3.
thinking again about the problem - i found ewarn is not enough - portage would handle the package as installed - not a good idea. is there a way to break out of an ebuild without blocking the installation of other ebuilds while updating and without making portage think it merged the ebuild?
*** This bug has been marked as a duplicate of 17367 ***
Add ACCEPT_LICENSES="RTCW-ETEULA" to the end of your /etc/make.conf and enjoy non-interactive goodness.
Closing to clean up after bugzilla upgrade. reopen if closed in error. Thanks.
clean up bug list after bugzilla update
