| 1 |
On 8/10/10 4:28 PM, Jeroen Roovers wrote: |
| 2 |
>> Gentoo uses /usr/$(get_libdir)/nsbrowser/plugins for browser plugins. |
| 3 |
>> However, Debian uses /usr/$(get_libdir)/mozilla/plugins, and that's |
| 4 |
>> what many software projects (including Chromium) target. |
| 5 |
> |
| 6 |
> Could you name them? Opera looks into tons of directories. |
| 7 |
|
| 8 |
Sorry, I used a weasel word "many software projects" without naming |
| 9 |
them. I don't know packages other than www-client/chromium that would |
| 10 |
have problems with this. |
| 11 |
|
| 12 |
> You would then need to re-emerge all users of this eclass. |
| 13 |
|
| 14 |
I see. This puts some burden for our users with no obvious gains. |
| 15 |
|
| 16 |
> What's bugging Chromium? Why does it insist on using a competing |
| 17 |
> browser vendor's name instead of the much more neutral "nsbrowser", |
| 18 |
> which generally denotes browsers with a Netscape style plugin interface? |
| 19 |
|
| 20 |
Well, the fact that every distributions chooses its own directory for |
| 21 |
NPAPI plugins is sort of sad. The number of directories that have to be |
| 22 |
searched for plugins is ridiculously long. |
| 23 |
|
| 24 |
I was talking with Evan Martin, a Chromium developer, and he asked |
| 25 |
whether Gentoo could switch to "mozilla/plugins", so I started this |
| 26 |
thread. After the results, my patch to add "nsbrowser/plugins" to the |
| 27 |
plugins search path is probably going to be accepted. |
| 28 |
|
| 29 |
By the way, I just wonder... why not _symlink_ "mozilla/plugins" to |
| 30 |
"nsbrowser/plugins"? That would solve the technical problem, while |
| 31 |
keeping a good, more general name. |
| 32 |
|
| 33 |
Paweł |
Archives