octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Windows installer


From: John W. Eaton
Subject: Re: Windows installer
Date: Fri, 10 Jan 2014 09:21:58 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131005 Icedove/17.0.9

On 01/10/2014 07:31 AM, Philip Nienhuis wrote:

While we're here, the build_packages script may require some changes:

1. Many developers here think that packages shouldn't be loaded by default.
So should the "-auto" flags be changed into "-noauto"?

I added -auto because I was trying to deliver something that would
have those packages loaded by default.  That's what my customer was
expecting.

3. The "-global" flag makes no difference, that is, not on my 3 Windows
boxes; it can be dropped I think unless it works or is required on Mac OSX.
Besides, the Windows installer makes shortcuts (Start Menu, desktop) for the
current user only.

Doesn't -global put the packages and the package list in a directory
under $OCTAVE_HOME instead of the user's $HOME?  If compiled packages
are included in the installer, then I think this is what we need.
Also, I recall that the package list file uses absolute path names, so
those need to be patched up by the installer to match the actual
location of the installed files.

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]