MSGID: 1:379/45 c7ca13d1
 REPLY: 1:379/45 de4d26e8
 TZUTC: -0500
 CHARSET: PC-8
From: "Rich Gauszka" 

mre  - meals ready to eat?

seriously I found this blurb

http://www.linuxpackages.net/view_comment.php?id=10076&cid=4111

Firefox 2.0 was tested thoroughly before I released it to Linuxpackages.net,
and it seems to run fine. I looked at the default startup script that you
referred to. The $moz_libdir and $MRE_HOME variables are only used if the
runtime directory cannot be found automatically. However, the runtime directory
is easily found by the script, so those variables are not necessary.


"Randall Parker"

wrote in message news:45861d0b$1{at}w3.nls.net...
> Mike N. wrote:
>> On Sun, 17 Dec 2006 14:59:25 -0800, Randall Parker
>>

>> wrote:
>>
>>> Of course. You get a shell script with the browser that you have to edit
>>> and copy to /usr/bin in order to upgrade Firefox. How user friendly.
>>
>>   I can't figure out why the paths are different from distro to distro -
>> must be one of those infathomable historical things.   "We'll never
>> establish a standard - that would be too much work for all those people
>> to
>> make a one time change to their paths".
>
> I am trying to figure out how to change the firefox script file. See this
> excerpt below. What the heck is mre?
>
> I did not change that line and I did change the moz_libdir to point to
> /opt/firefox-2.0 (where I put it) and that let FireFox start. Still, what
> is mre?
>
> #uncomment for debugging
> #set -x
>
> moz_libdir=/usr/local/lib/firefox-2.0
> MRE_HOME=/usr/local/lib/mre/mre-2.0
>
> # Use run-mozilla.sh in the current dir if it exists
> # If not, then start resolving symlinks until we find run-mozilla.sh
> found=0
> progname="$0"
> curdir=`dirname "$progname"`
> progbase=`basename "$progname"`
> run_moz="$curdir/run-mozilla.sh"

--- BBBS/NT v4.01 Flag-5