emerging mpg123 fails when neither nas, esd, or oss are not set in USE... instead of warning and stopping, requesting that the ebuild warn, select OSS as default, and continue... imho, if one is using nas or esd, those would probably be set in USE already... encountered this minor annoyance when it stopped an emerge -e world after a USE flags cleanout. Reproducible: Always Steps to Reproduce: 1. do not set nas, esd, or oss in USE 2. emerge mpg123 3. Actual Results: emerge warns and stops Expected Results: preferred: warn and continue simple feature request
fixed in portage.