[Pkg-octave-devel] Changing pkg-octave-dev to parse config files

[Ólafur Jens Sigurðsson]

On Sun, Apr 27, 2008 at 09:33:47PM +0200, Thomas Weber wrote:
> On 27/04/08 19:56 +0200, Rafael Laboissiere wrote:
> > * Thomas Weber <thomas.weber.mail at gmail.com> [2008-04-27 10:01]:
> > 
> > > we currently start up octave for building forge package with the
> > > following options:
> > > 
> > > octave_options = --norc --no-history --silent --no-site-file
> > > 
> > > I would like to drop the "--norc" part, such that the system wide config
> > > file (/etc/octave.conf) is parsed.
> > 
> > In this case, we should also drop --no-site-file
> 
> Upps, you are right.
> 
> octave's help says the following:
>   --no-init-file          Don't read the ~/.octaverc or .octaverc files.
>   --no-site-file          Don't read the site-wide octaverc file.
>   --norc, -f              Don't read any initialization files.
> 
> So, does this mean that "--norc == --no-init-file --no-site-file"?
> 
> > What about replacin "--norc --no-site-file" by --no-init-file?  I do not
> > remember well, but I think that one of the goals of using --norc was to
> > avoid ~/.octaverc being loaded.
> 
> --no-init-file should work. But I guess if we have a ~/.octaverc file in
> the build chroots, there's something screwed to begin with.

Jup, there shouldn't be any .octaverc files around in the chroots so
that shouldn't be a neccissity to exclude but doesn't harm either.

Is there any specific reason you want the system wide configurations
file parsed Thomas? Just wondering and it is nice to have it for the
record since the next time people wonder about this then the argument
can be looked up :-)

Oli