[REBOL] Re: rebol and boot path
From: petr:krenzelok:trz:cz at: 29-Jun-2001 23:35
> PK> 2) is the current aproach really practical?
> Yes, and can be used on multiuser platform.
No, it isn't, unless ... se below :-)
> PK> Let's say some externall app launches your rebol, so
> PK> e.g. apache, so you inherit launcher app directory and you have to
> PK> specify e.g. c:/pekr/rebol/command/rebol.exe -cs
> PK> c:/pekr/rebol/command/my-script.r and you are left with following
> PK> problems:
> PK> a) it will look for user.r file in launcher app directory
> Yes, but if it is not there (with rebol.r) it will look in env var.
> PK> b) try to use
> PK> View and -i switch - it will be ignored (which I reported being a bug)
> PK> and you will end up with installation screen. View needs two
> PK> files, or it will try install itself ...
> Set REBOL_VIEW to /path/to/view .
OK, then answer two following cases:
1) I want to start rebol process once I log into Netware server. I put
following line into my login script:
#F:\path\to\rebol -si F:\path\to\rebol\some-script.r
... and you know what? You will be asked for installation, even if -i switch
was used. I can't see it correct, not even practical. If -i switch is
supposed to save us from installation, it should do so in all cases.The
problem is with edit-prefs.r and prefs.r, which are needed. But how do I
tell rebol to look for them on the path given in above launch case? ;-)
where first line of bat is "cd current-dir"
2) How do env variables help you, if you use several instances of View on
workaround & suggestion - introduce new switch -b (boot), to allow us to
specify, what directory should rebol boot from ...