Re: Windows installer replaces the PATH variable

[Elliott S. <ell...@gm...>]

On Thu, Apr 21, 2011 at 1:11 AM, Anton Vodonosov <avo...@ya...>wrote:

>
>
> 21.04.2011, 11:20, "Elliott Slaughter" <ell...@gm...>:
>
> > I'm hoping to at least find a way to check dynamically if the string is
> too long and avoid smashing PATH. I don't know if there will be any better
> solution until a new version of NSIS comes out.
>
> An idea: try to set some temporary env variable, and then read it's value.
> It the variable wasn't smashed, then PATH will not be smashed too.
>

Anton, could you try this fix?

http://elliottslaughter.net/files/clisp-2.49+-win32-install-fix2.exe

The installer script is identical to the last attempted fix, but I used the
8192-length-strings version of NSIS.

I decided not to add a dynamic check since past 8192 the Windows command
line breaks anyway. I did add a compile-time check so that we can be sure
the maintainer is using this special version of NSIS.

The fix tested out fine on my machine, but I'll wait for independent
confirmation before pushing the fix.

-- 
Elliott Slaughter

"Don't worry about what anybody else is going to do. The best way to predict
the future is to invent it." - Alan Kay