1. A tarball install of Firefox-4.0b9 installs as: "firefox",
yet the startup shell script ./firefox/firefox lists: "firefox-4.0b9"
moz_libdir=/usr/lib/firefox-4.0b9
Consistency reduces confusion, failures, and costs. For those of us in
multi-user enterprise environments, managing multiple releases over time, the
extended nomenclature is preferred. This enables multiple releases to co-exist,
certainly wise given stability issues of rapid releases.
2. The following code block seems problematic. First, it hard-wires an
assumption that may not be logically consistent with other issues (see Flash
libssl3.so , et. al., issue) (see secure application installation issue).
Further the variable definition of moz_libdir may be a paste-on fix to address
a particular problem. Yet the immediately following code block seems to resolve
the core program location. Pushing moz_libdir resolution into this blocks seems
logical.
----
#uncomment for debugging
#set -x
moz_libdir=/usr/lib/firefox-4.0b9
# Use run-mozilla.sh in the current dir if it exists
# If not, then start resolving symlinks until we find run-mozilla.sh
----
--
This message posted from opensolaris.org
_______________________________________________
desktop-discuss mailing list
desktop-discuss@opensolaris.org
