The chromium (or chromium-bin) ebuilds) should never touch, replace or modify the plugins directory if it is not what was defined by a previous ebuild. Reproducible: Always Steps to Reproduce: 1. chromium is sensitive to the contents of the plugins directory 2. gentoo ebuilds tend to create a symlink between .../chromium*/plugins -> /usr/lib/nsbrowser/plugins 3. I recreate specific plugins directory with only those plugins that chrome can handle. 4. A chromium ebuild should never ever mess with a user defined plugins directory. Actual Results: Chromium installs destroy user-defined plugins directories and symlinks. Linking to /usr/lib/nsbrowser/plugins causes chromium to become exposed to mozplugger.so (which is installed on my system for Seamonkey/Firefox) which in turn exposes chrome to the defunct process problem (Chrome Issue #23778 (and several others)). Gentoo ebuilds should only override user "adjustments" at the behest of the user. Otherwise there is an incentive to freeze the ebuild process at something that works (masking upgrades). Expected Results: Ebuilds/installs must be sensitive to user preferences. It would be strongly advisable for Gentoo to do *nothing* with the chromium plugins directory but simply advise the user on how to set it up carefully. A separate issue is that Chromium may go off on a "witch hunt" for plugins, esp. flash) and will search several/all (/usr/lib/*/plugins) directories for plugins. That is a real problem if one is trying to prevent chrome from trying to access flash or mozplugger.so. Though I am not opposed to flash or other plugins, I prefer to use them on a case by case basis. That means that chromium is ultimately going to require FlashBlock (currently available) as well as NoScript (not available) as well as some future HTML5-Video-Block (not available). Because its my DSL line and one cannot transmit video effectively over a DSL line and it should be my decision whether to max out my DSL line (to say nothing of a dial up line) for video (much of which I may have no interest in). Browsers should never force feed users.
I guess a USE flag will satisfy you. It's going to be on by default since that's what I assume most users want anyway.
Done and tested. Enjoy!
