Re: any impacts of adding this line to default .octaverc ?

[Philip Nienhuis]

NJank wrote
> (related to bug 51632, about Windows users not knowing they have to run a
> pkg rebuild if they use the (sort of portable) zip installer:
> 
> would it ever cause problems if Octave was set to run a 'pkg rebuild' on
> startup if it detected there was no global octave_packages file?  Seems to
> be the simplest way to modify that build to remove the need for the manual
> operation.
> 
> something like:
> 
> if (isempty(file_in_path(fullfile(OCTAVE_HOME(), "share", "octave",
> "packages"), "octave_packages")))
>   pkg rebuild;
> endif
> 
> 
> or
> 
> if (exist(pkg("global_list"),"file") == 0)
>   pkg rebuild;
> endif
> 
> 
> https://savannah.gnu.org/bugs/index.php?51632

There's always a remote possibility that the unzipped Octave installation is
in a read-only location. In that case octave_packages cannot be created in
OCTAVE_HOME. A simple try-catch around the "pkg rebuild" line could serve as
a band-aid. 

Philip




--
View this message in context: 
http://octave.1599824.n4.nabble.com/any-impacts-of-adding-this-line-to-default-octaverc-tp4684287p4684305.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.