[Pkg-octave-devel] Changing pkg-octave-dev to parse config files
Thomas Weber
thomas.weber.mail at gmail.com
Sun Apr 27 19:33:47 UTC 2008
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.
Thomas
More information about the Pkg-octave-devel
mailing list