On Tue, Aug 10, 2010 at 7:28 PM, Jeroen Roovers wrote: > On Tue, 10 Aug 2010 14:29:20 -0700 Paweł Hajdan, Jr. wrote: >> Why are we using nsbrowser/plugins instead of mozilla/plugins, and how >> relalistic would it be to switch to mozilla/plugins? > > --- nsplugins.eclass 1 May 2009 23:03:00 -0000 1.24 > +++ nsplugins.eclass 10 Aug 2010 23:21:19 -0000 > -PLUGINS_DIR="nsbrowser/plugins" > +PLUGINS_DIR="mozilla/plugins" > > You would then need to re-emerge all users of this eclass. > > All I want to ask is why? In fact *most browsers* have no trouble > finding plugins, and provide options through which you can inform them > where the plugins might be. > > What's bugging Chromium? Why does it insist on using a competing > browser vendor's name instead of the much more neutral "nsbrowser", > which generally denotes browsers with a Netscape style plugin interface?
indeed. we've been using nsbrowser/plugins literally for 8 years and no one has complained. i dont think "mozilla" is an improvement over "nsbrowser". -mike