[Octave-bug-tracker] [bug #45188] MXE: problems installing different Octave versions side by side

[Philip Nienhuis]

Follow-up Comment #17, bug #45188 (project octave):

Yes I clearly remember the course of this bug :-)  and indeed the title
doesn't reflect the current issue.

Currently I have a "plain" development version installed that I update
~weekly, and now I want to test patches supplied by Dan w/o having to
uninstall + reinstall Octave + all packages. 
IOW I have a working 4.1.0+ version plus I want to install a test
Octave-4.1.0+ into another install directory. That doesn't work.

Could that registry part be avoided at all? E.g., notepad++ offers to use .ini
files rather than the registry. AFAIK Octave only uses it for uninstalling
itself, and -passively- for locating Java.
"Wiping" the Octave registry entries (i.e., removing it through Control Panel
| Programs after having temporarily renamed the install directory) still
allows the uninstall program to do its job fine.

Separate registry keys for 32 or 64 bit, esp. for normal users, look over the
limit to me.

My main problem is the "hard" refusal to install - there should be a way
around it (IMO, that is).

It isn't easy to change the version number as AFAICT that should already
happen when (on the Linux side) building the dist archive ("make all dist")
used to build mxe-octave upon, as mxe-octave extracts the version from
Octave's dist archive.

Of course for the case at hand I can also make a tardist/zip, unpack that and
add the shortcuts etc by hand.

Manually adapting the version in makeinst_script.sh is another option; or
maybe another make option that adapts makeinst_script.sh.

(BTW another wish is to be able to specify the Start Menu subdir for the
shortcuts - I'll open a separate bug report/feature request for it or I'll
come up with an makeinst_script.sh patch myself in the patch tracker.)

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45188>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/