|
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: | Sat, 2 Nov 2019 19:26:11 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 |
Follow-up Comment #43, bug #51632 (project octave): Short file names don't work as you apparently think they do. They're not stored in the file system but used internally in user programs. NTFS or FAT32 makes no difference - internal Windows system calls are used to translate short file names to LFN and vice versa at or near the application level, not quite at the file system level. If you'd install Octave in a subdir with a name with -say- 15 characters, you'd see that '__octave_config_info__ ("bindir")' echoes a short path name. If you were to use a DOS program (even on Win10 supported through DOSBOX) you'll see that the DOS program also morphs LFN pathames into short (8.3 style) path names. Short file names help a lot for MSYS / MSYS2 calls to cope with spaces in path names, that's why JohnD implemented them in the NSIS installer. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?51632> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |