On Dec 8, 11:41 pm, Alexey Borzenkov <
sna...@gmail.com> wrote:
> Jon, is there any way to modify the installer to fall back to reading
> PATHEXT from HKLM if value in HKCU is not there? I looked at master
> and it seems that it reads PATHEXT from HKCU, chops it into a list
> (empty string results in empty list I suppose) and merges the
> resulting empty list with .rb/.rbw, thus source of the problem.
This might be the problem, but it was originally reported that PATHEXT
was set on the system level only and the environment variable still
had some different value. If it were the case, it would be reported
that PATHEXT was set to .eb;,rbw at the user level. So, it is
necessary to double check that.
Jon, if ever possible, please do not modify the installer so that it
fells back to HKLM. For example, I have manually set EXTPATH in HKCU
to %PATHEXT%;.rb;.rbw long ago when I compiled Ruby from source. If I
run the installer with empty HKCU, I would like it to do the same.
More so, if I run the installer with the current setting, being
Administrator or not, I would like it to be unchanged.
Why not to take the safe path: if the installer ever wants to modify
HKLM, it should always run with elevated privileges. The only reason
to do so I see is to install Ruby for all users. Possibly the
installer should just ask that. Depending on the answer, only HKLV or
only HKCU should be modified. I do not see any reason for any
fallback.