Re: octaverc and version in path?

[Thomas Treichl]

Ben Abbott schrieb:
> There has been a discussion on the help list regarding ".octaverc" and 
> the version specific path structure.
>
>     http://www.nabble.com/path-3A-octave-3.0.0-can-27t-find-itself-to14506843.html 
>
>
> Below is an example of the contents of .octaverc taken from an install 
> of Octave 3.0.0 on Mac OS X.
>
> Begin forwarded message:
>
> > ## Begin savepath auto-created section, do not edit
> >  path ('.:
> >         /Users/dushanm/Octave:
<SNIP .octavrc file>

Dushan,

I had a look at it. If Octave.app starts up then there is a very similar path 
setting than you do manually in your .octaverc file. However, with the 'path' 
command you are overwriting the complete path variable that was set up before or 
while startup. Therefore a solution for your problem is to have something like 
the following code as your .octaverc file:

  ## .octaverc starts here
  addpath (genpath ('/Users/dushanm/Octave'));
  ## end of .octaverc file

The only line of code that is evaluated here "adds" the folder 
'/Users/dushanm/Octave' and all subfolders within '/Users/dushanm/Octave' to 
your path setting (and does not overwrite the other path setting that was made 
before). This is all that you need, if not then please let us know once again.

> This inclusion of the path presents some problems. For example, the 
> .octaverc is not upgraded when octave is, and produces a conflict in the 
> event a user wants to install different versions of octave.
>
> I assume the version information is there for a reason, what is that 
> reason?

Ben,

this feature can be used to run different Octave versions parallel if installed 
correctly and without the need to delete older versions.

*NOTE* It is not possible to set up more than one Octave.app in one and the same 
folder without modification of the startup scripts. Changing the name of 
'Octave.app' is a no-no because the name 'Octave.app' is the identifier for the 
startup scripts resp. the place of the directory structure where Octave.app is 
found.

> Might something be done regarding how the path is handled to facilitate 
> the upgrade process, and perhaps allow for installations of multiple 
> versions?

As described before.

  Thomas