John Fischer wrote:
> This project proposes to back port Firefox 3.0.x from Nevada to a
> Solaris 10 Update release which is a Patch release of Solaris.
Is it integrating into the update release or shipping as a separate
web download running on top of the update release? (/opt would be
wrong for the integrated case, right for the unbundled case).
Is this intended to replace or supplement Firefox 2.x?
The one-pager references both /opt/firefox3 & /opt/sfw/lib/firefox/ - can
we assume /opt/firefox3 is correct since /opt/sfw is reserved for the
Solaris Companion CD?
> All the plugins are spawned by firefox-bin. So, LD_LIBRARY_PATH
> environment variable will be set to /opt/sfw/lib in run-mozilla.sh
This also seems incorrect - should this refer to the /opt/firefox3/lib
directory or are you importing/depending on libraries from the Companion CD?
(Also, in the unavoidable cases in which you must use LD_LIBRARY_PATH-type
variables, you should always use LD_LIBRARY_PATH_32 or LD_LIBRARY_PATH_64
to avoid breaking programs of the other wordsize.)
Are the library upgrades incompatible? Is there no way they can be
shipped as updates to the existing public libraries in /usr/lib ?
For the brand new libraries, like cairo & dbus, is there any architectural
reason they must be private, or is this just a resource issue around supporting
them?
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
