[REBOL] Re: 'launch and scripts running other scripts.
From: holger:rebol at: 1-Jan-2002 10:43
On Tue, Jan 01, 2002 at 09:10:08AM +0100, Jean-Francois BOUZEREAU wrote:
> The macintosh version of rebol/view also insists on
> creating FIVE copies of the executable the first
> time it runs. It is very irritating, and I cannot
> find any reason for doing that. If you try to delete
> them, they are automatically re-created at the
> next run.
This is necessary in order to support "launch". Unfortunately
MacOS does not allow an application to run multiple processes
from the same binary, so REBOL/View needs to duplicate the binary
a few times in order to allow more than REBOL/View process to run
> The unix version has another ennoyance. When it
> runs for the first time, it apparently wants to
> rewrite the executable file. It is OK if you
> have your own version of the program, but if you install
> rebol in a well known directory (/bin or /usr/bin
> for example) for a public usage, rebol stops
> and complains about the rebol file being not
> found or not writable.
This will be improved in the next version. Again, the
reason is launch. For that REBOL/View needs to know where it is
installed. At the moment the file that contains that
information is ~/.rebol, in the user's home directory. If
that file does not exist then REBOL/View assumes it has not been
installed and attempts to copy the binary over to the
We realize this does not work well in the kind of
situation you describe. There should probably be a
file /etc/rebol.rc that contains the same kind of
information as ~/.rebol, but system-wide, in situation
where REBOL/View is installed by an administrator.
Just for completeness: the installation information for
Windows is contained in the Windows registry. For
AmigaOS it is in L:.rebol
> RT says that rebol is very easy to install, just
> copy and run, but I do not agree.
For /Core. For /View the situation is different because
of features such as "launch".