[Octave-bug-tracker] [bug #58313] [octave forge] (parallel) should use octave-cli-VERSION executable by default

[Mike Miller]

URL:
  <https://savannah.gnu.org/bugs/?58313>

                 Summary: [octave forge] (parallel) should use
octave-cli-VERSION executable by default
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Wed 06 May 2020 01:20:28 PM PDT
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: GNU/Linux

    _______________________________________________________

Details:

In both local and remote parallel modes, the parallel package runs Octave as
the 'octave-cli' binary. However, this command name is not safe,
'octave-cli-${OCTAVE_VERSION}' should be used instead.

Example on a system where the 'octave-cli' symlink does not exist in the same
directory as 'octave-cli-6.0.1':


>> y = parcellfun (...)
open: No such file or directory
couldn't set executable
open: No such file or directory
couldn't set executable
error: can't reset scheduler
error: called from
    parcellfun at line 117 column 9
    pararrayfun at line 85 column 28


Example on a system where the 'octave-cli' symlink exists but points to a
different version of Octave that doesn't have the parallel package installed:


>> y = parcellfun (...)
error: package parallel is not installed
could not load variable
could not save variable.
error: package parallel is not installed
could not load variable
error: __parcellfun_initialize_job__: could not initialize job
error: called from
    parcellfun at line 181 column 7


I'm aware that the Debian and Ubuntu packages only install
/usr/bin/octave-cli, without the version suffix, but maybe that target can be
treated as a special case, either detected at install time or at run time. In
general, if you want to handle both possibilities, I'd think that
'octave-cli-${OCTAVE_VERSION}' should always be preferred if it exists.




    _______________________________________________________

Reply to this item at:

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

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