Hi all,
There is a couple of issues with the Mozilla instructions that I'd
like to get input from anyone interested, or anyone who wants to
suggest an idea. I realize Mozilla may be a thing of the past, now
that Seamonkey is available, but I believe both of these may still
be applicable after a switch to Seamonkey.
1) There are some programs (OpenSC, librsvg, swfdec, etc.) that create
Mozilla-compatible plugins and install them into /usr/lib/mozilla/plugins.
This sort of creates an issue with what exactly to do about this plugin
directory if you install a Mozilla-based browser, which creates
/usr/lib/firefox-1.5 or /usr/lib/mozilla-1.7.12 directory structures.
There are some instructions in the book right now that try to cover for
this, but they are broken (in situations where /usr/lib/mozilla/plugins
is not a directory). Here are some revised commands, with comments so
to explain them:
===============================================================
# If /usr/lib/mozilla/plugins or /usr/lib/mozilla are symlinks
# they are deleted so that a directory can replace it.
#
if [ -L /usr/lib/mozilla/plugins ]; then
rm /usr/lib/mozilla/plugins
fi &&
if [ -L /usr/lib/mozilla ]; then
rm /usr/lib/mozilla
fi &&
# Create a new plugin directory if it doesn't already exist
#
install -v -m755 -d /usr/lib/mozilla/plugins &&
# Copy the newly installed plugins to the new directory
#
cp -v /usr/lib/mozilla-1.7.12/plugins/* /usr/lib/mozilla/plugins &&
# Remove the recently installed plugins directory
#
rm -f /usr/lib/mozilla-1.7.12/plugins &&
# Replace the just removed directory with a symlink pointing
# to the plugin directory created and populated earlier
#
ln -v -s ../mozilla/plugins /usr/lib/mozilla-1.7.12 &&
=====================================================================
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.
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"?
The instructions for the plugins above break the ability to do this.
Any input on either question would be appreciated.
--
Randy
rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3]
[GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686]
08:59:00 up 131 days, 18:23, 3 users, load average: 0.00, 0.00, 0.04
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
