Re: Windows installer

[Philip Nienhuis]

John W. Eaton wrote
> 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.

OK, so we're overruled :-)


>> 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.

Ah, I now realize that "-global" is simply the default; it does put OF
packages in the <OCTAVE_HOME>/[share|lib]/octave/package hierarchy.
"-local" tries to put it in the "HOME" dir (actually %USERPROFILE%\octave),
indeed.

On Windows I'd prefer to have OF packages in the OCTAVE_HOME hierarchy. I
use several Octave versions next to each other and they aren't fully
compatible, not even at m-file level.

Philip



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Windows-installer-tp4660695p4660923.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.