[Octave-bug-tracker] [bug #45872] default site octaverc file still executed even if OCTAVE_SITE_INITFILE is defined

[Rik]

Update of bug #45872 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #1:

Confirmed.

I instrumented all the rc files including scripts/startup/main-rcfile,
scripts/startup/local-rcfile,
<OCTAVE_INSTALL_DIR>/share/octave/4.1.0+/m/startup/octaverc,
<OCTAVE_INSTALL_DIR>/share/site/m/startup/octaverc, ~/.octaverc, ./.octaverc
with the following code:


printf ("Executing %s\n", mfilename ("fullpathext"));


If I now use the run-octave script I get the following:


Executing /home/rik/wip/Projects_Mine/octave-dev/scripts/startup/main-rcfile
Executing /home/rik/downloads/local/share/octave/4.1.0+/m/startup/octaverc
Executing /home/rik/.octaverc
Executing /home/rik/wip/Projects_Mine/octave-dev/.octaverc


This seems to be expected behavior, although not necessarily correct.  The
run-octave script overrides OCTAVE_SITE_INITFILE which is startup/main-rcfile.
 But 'make install' places main-rcfile into the versioned site file
octave/4.1.0+/m/startup/octaverc.  To eliminate running main-rcfile twice the
variable OCTAVE_VERSION_INITFILE needs to be pointing somewhere else.

Or, we have had this wrong for several years and the local-rcfile should be
placed into the versioned directory and the main-rcfile should be placed in
the startup directory.

For clarity, I think it would be a good idea to rename the files from
[main|local]-rcfile to [site|version]-rcfile.  At least then it will be clear
what we are doing with these files.


    _______________________________________________________

Reply to this item at:

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

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