On 2/3/06, Randy McMurchy <[EMAIL PROTECTED]> wrote: > > Okay, you may wonder, why don't we just do like the Firefox > instructions and tell folks that if they have existing plugins in > /usr/lib/mozilla/plugins to copy (create links, whatever) them into > /usr/lib/mozilla-1.7.12/plugins and not worry about all those > commands? > > This could be done. I'm looking for suggestions.
I prefer this way. What if plugins such as libnullplugin.so are incompatible between Mozilla-1.7 and Firefox-1.5? I think there's plenty of information in the book about the plugins. If someone wants to create a central repo of plugins in /usr/lib/mozilla/plugins, I think they can figure out how to do this. > 2) Do we need to continue to maintain this support for broken > programs (don't check pkgconfig files) that currently in the book > we make /usr/lib/mozilla and /usr/include/mozilla symlinks to the > appropriate versioned directories so that "programs don't have to > know which version of Mozilla is installed"? You may have two versions of the mozilla based browser that have incompatible backends (1.7 vs. 1.8). So, I'd prefer if these packages were patched so that they install into the specific plugin directory of the libraries they were compiled against. For example, if you compile librsvg against firefox-1.5 by passing --with-mozilla=whatever, then I think the plugin in should go into whatever's plugin dir. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
