[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: Sun, 3 Nov 2019 04:37:58 -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 #47, bug #51632 (project octave):

OK, I got it wrong here, I stand corrected :-) 
Thanks for the pointer.

Just curious: if you install Octave on that D:-drive (from the binary
installer [*]) in a path with a fairly long file name, what does OCTAVE_HOME
I'm asking because AFAIK it's inside the NSIS installer where these 8.3 path
names are created, and thus where much of this confusion comes from (the rest
comes from pathseps). If that won't work on such an NTFS drive there may be
another bug looming.

[*] If you want to try, a eperimental cross-build from Nov 2 is here:
(up until cset 27615:83c1d4f75a36, but with local mods and incl. patch from
comment #36)


Reply to this item at:


  Message sent via Savannah

reply via email to

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