Re: octaverc and version in path?

[Daniel J Sebald]

Ben Abbott wrote:

> 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?
>
> Might something be done regarding how the path is handled to  facilitate 
> the upgrade process, and perhaps allow for installations of  multiple 
> versions?

OCTAVE_VERSION has been around fairly long.  Could one test that variable 
inside .octaverc?

Dan