On Fri, 24 May 2002 15:36:34 -0700 Graham <[EMAIL PROTECTED]> wrote:
> Mikus Grinbergs wrote:
>
> Try sticking this lot in a .cmd file and running it from a command line:
>
>     <suggested .cmd file - deleted by Mikus for brevity>
>
> Please note that it is by no means fully tested, and certainly not
> guaranteed to do anything other than consume a small amount of disk
> space, but it works here. I'll listen to helpful and constructive
> comments telling me it doesn't work, but no whining!

My apologies, but I'll whine!  (And I'm replying to the newsgroup
because you did not supply an address to which I could respond.)


My major stumbling block is that you are suggesting a script (.cmd
file) to use during *installation* of a browser build.  I already
have to remember which script (or more generally, icon) to use to
*run* the browser build (there are at least eight browser versions
that I use from time to time).  I don't want to clutter up my mind
by having to remember even more browser-related scripts.

Then there is the matter that if I *did* have a script for Mozilla
installs, I should *expand* that script to cover all the other
things I am doing manually -- update prefs.js, update mimetypes.rdf,
update bookmarks.html, copy files into plugins, etc., etc.  Though
such a script would save time and effort, I'm installing maybe every
five days.  Designing (and later, maintaining) a script for such
occasional use does not offer me enough of a sense of accomplishment.

The script you suggested shows that you and I have WAY different
starting points.  You assume that MOZILLA_HOME is available when I
am installing a Mozilla build.  On my system it is not.  I do my
install from a command-line session from which I manipulate the
Mozilla files as though they were data.  Then, in a separate
session, I *run* the browser build I installed.  (In fact, part of
my installation process is to choose what __value__ for MOZILLA_HOME
I should stick into the run-time script used to launch that build,)

Thank you for your suggested .cmd, but I'll pass.

mikus


Reply via email to