* Contents of www-plugins/chrome-binary-plugins-54.0.2840.100: /usr /usr/lib64 /usr/lib64/chromium It's not much of an "update" for a package to remove the only reason it was installed in the first place. The package should really fail with an explanation, rather than just installing an empty shell, and point users to adobe-flash instead. As is, I had to search around the web to find out I now needed a different package to provide the exact same files.
To be fair, flash got removed from the google-chrome deb files before we had any idea that Adobe would start publishing a PPAPI version of flash themselves. I don't think it makes sense to restore the flash USE flag just to display an error message.
Not sure if this is a new bug or a reflection on the overall problem. If I have "widevine" enabled as a global USE flag, the deps for www-apps/chromium try to pull in chrome-binary-plugins, which conflicts with the file that www-apps/chromium installs itself. I'll be glad to open another bug if this problem is unrelated. However, it seems like how this USE flag is applied when globally set should be revisited. Thanks.
Just a stupid thought; wouldn't it make sense to add following line to have at least one useflag enabled, would it? REQUIRED_USE="|| ( ${IUSE//+} )" Is it necessary to escape that '+' sign?!
