Now that portage (2.1_pre4) allows default emerge options to be set in make.conf, there's a possible issue with esearch/esync: if EMERGE_DEFAULT_OPTS="--ask", then esync, which captures console output from emerge --sync, will wait for user confirmation that will never come. It should either pass that request for confirmation on to the user or unset EMERGE_DEFAULT_OPTS for the duration of its run.
I agree. I think there should be a commandline switch to tell emerge to ignore the default opts. I realize it is possible to unset EMERGE_DEFAULT_OPTS for a given run of emerge, but having a --nodefaults flag or something similar would be cleaner. In the past I aliased emerge to work with whatever commandline flags I wanted, and then it was a simple matter of using the absolute path to emerge to override the flags. It would be nice if portage could do something similar with the EMERGE_DEFAULT_OPTS variable.
EMERGE_DEFAULT_OPTS is not an incremental so this can be done by setting the var to empty in the environment in which emerge is started.
(In reply to comment #2) > EMERGE_DEFAULT_OPTS is not an incremental so this can be done by setting the > var to empty in the environment in which emerge is started. > I can confirm that works for me, and as I call esync from a script (that also updates my overlays) it's a good solution for me. Still, esync should be updated to do the same thing.
Fixed in esearch-0.7.1-r3
