octave-maintainers
[Top][All Lists]
Advanced

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

Re: build_packages.m script, visibility?


From: Oliver Heimlich
Subject: Re: build_packages.m script, visibility?
Date: Sat, 26 Dec 2015 00:18:31 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.4.0

On 26.12.2015 00:11, Nicholas Jankowski wrote:
> I always install via the zip file version and don't run into any admin
> issues with packages. Can anyone comment if this is always the case, or
> only for certain packages? Same problem with the pkg install or pkg
> update commands?

This is because you installed Octave in C:\Octave\… and I did install it
(with higher privileges) in %ProgramFiles%.  Later, when running it
again, I do not have permission to unzip / install packages in
%ProgramFiles%

> Having it install the default when the program is installed would
> (should) be easier as it should occur with the same access level used to
> run the Octave installer.

Yes, this would eliminate a lot of pitfalls.

> Would this happen by opening an instance of Octave set to run the build
> packages script and exit? Can they be "built" before building the
> installer so they're already installed?

As far as I understand, the packages are cross-compiled, but
build_packages.m does not consider this possibility and does a “classic”
installation. It would suffice to extract the tarballs, put the files
into the right directories and update the global package database. This
should be possible to do with the installer and not run an Octave script
during installation.

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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