octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #53124] [MXE Octave] install in path that incl


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #53124] [MXE Octave] install in path that includes spaces
Date: Sun, 25 Oct 2020 05:59:05 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36 Edg/86.0.622.51

Update of bug #53124 (project octave):

                  Status:          Ready For Test => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #36:

Imho, it is a good thing that Octave core files cannot (accidentally) be
changed by default. A "normal" user shouldn't do that. They are obviously
still allowed to inspect, change and re-distribute the code according to the
GPL. But (accidental) changes to core or package files might lead to
unexpected results and difficult to reproduce bug reports. This is especially
true if multiple users share one installation.

If a user would like to be able to edit .m files from the core or distributed
packages (without elevated privileges), they can select a different
installation directory in the installer, select a local installation, or use
the .7z or .zip packages.
It is always possible to view the code, and users can still edit the files
with elevated privileges when installed at the default location.

Btw, this is the same when Octave is installed at the default location (in
/usr) on Linux.

FWIW: Only a very small portion of the functions included in Matlab are
p-coded. But for obvious reasons, Octave developers should still refrain from
inspecting Matlab's .m files. (It's different for functions that are
implemented by TheMathworks in C or a different compiled language. The source
code of these functions is *not* available.)

Octave seems to work correctly (and more similarly to a default installation
on Linux) with the new default installation location. If major problem should
appear, we could re-open this report.
Other issues (which would probably apply cross-platform) should be tracked in
dedicated bug reports.

Closing as fixed.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?53124>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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