[Top][All Lists]

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

[Octave-bug-tracker] [bug #51632] make global pkg paths always relative

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #51632] make global pkg paths always relative to OCTAVE_HOME, no need to pkg rebuild -global when path changes
Date: Fri, 8 Nov 2019 13:52:16 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4

Follow-up Comment #53, bug #51632 (project octave):

(Returning after a few distractions)

About 8.3 vs LFN path names comment #41:
I'm afraid no call to canonicalize-file-name can be dropped.
The 8.3 style file names are deep in the mxe-octave installer. See for

>> [a, b] = pkg ('prefix')
a = C:\Programs\Octave\OCTAVE~1.0_2\mingw64\share\octave\packages
b = C:\Programs\Octave\OCTAVE~1.0_2\mingw64\lib\octave\packages
ans = C:\Programs\Octave\OCTAVE~1.0_2\mingw64

This feature request is about relocating unzipped mxe-octave installations. I
think prebuilt packages in such installations are installed in OCTAVE_HOME
anyway so prefixes would seem to be less relevant at first sight.
But to make the patch more general I think I'll make the pkg paths relative to
the prefix and archprefix. In mxe-octave installers and zipdists it won't make
any functional difference. The verbatim block above shows how OCTAVE_HOME is
part of those prefixes in mxe-octave installations anyway.

A first final cset would be for Octave itself, I hope to come up with one this

The next step is patching mxe-octave to produce an octave_packages file in the
installer and zipdist archive. Shouldn't be too hard but needs some sorting
out; perhaps JohnD can help if I get stuck.


Reply to this item at:


  Message sent via Savannah

reply via email to

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