octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RC2 / 5.0.91


From: Andrew Janke
Subject: Re: RC2 / 5.0.91
Date: Thu, 7 Feb 2019 14:59:01 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.5.0



On 2/7/19 2:45 PM, Mike Miller wrote:
On Thu, Feb 07, 2019 at 14:15:04 -0500, Andrew Janke wrote:
I wonder if, for the test suite, the system and/or site octavercs should be
treated differently from the user octaverc, because this might be used to
make configuration changes for Octave to work correctly in the environment
in which it's installed?

In that case, you can choose to run the test suite with octave
--no-init-file. This loads the system startup files but avoids loading
user startup files.

Thanks.

I feel like this subthread is trying to define a strict environment that
the test suite should always be run in. IMHO that is not the right
direction at all. The test suite should be run in the user's normal
working environment.

I fully agree with this. It would be best if the test suite ran everywhere, and it used mechanisms to insulate itself from irrelevant variability in the preference/environment state.

Thoughts on how to handle this? Should site octaverc still be run when doing
test suite runs? Is Octave.app doing the Right Thing by relying on the site
octaverc to do important tool configuration?

Yes, I think this is exactly the right thing.

Thanks. Will continue to do so.

Cheers,
Andrew



reply via email to

[Prev in Thread] Current Thread [Next in Thread]