Use the lappendConf procedure to set the locked_configs option and the
setConf procedure to set the avail_report_dir_sym and
avail_report_mfile_sym options.
Add an utility library that supersedes the closedir function from libc.
The closedir function from this added library always returns an error
(-1). It is used for coverage test of the closedir call made withing the
Envmodules_GetFilesInDirectoryObjCmd function of the Tcl extension
library.
Add a ``verbosity`` configuration option to define the default message
verbosity level (between a ``normal`` and a ``debug`` level). This
option could be set at ``./configure`` time with ``--with-verbosity``
option. It could be superseded with the ``MODULES_VERBOSITY``
environment variable, that could be set with ``config`` module
sub-command through the ``verbosity`` option.
Defining a ``debug`` verbosity level at the command-line level is still
achieved by using the ``-D`` or ``--debug`` command-line switches.
Add to the configure script the --with-locked-configs option to ignore
environment variable superseding of Modules configurations defined in
modulecmd.tcl script. Lockable configuration option are extra_siteconfig.
Currently locked options are reported through the locked_configs option
on the config sub-command.
This new configure option replces --enable-extra-siteconfig which was
dedicated to the control over the MODULES_SITECONFIG variable.
Add to the configure script the `--enable-extra-siteconfig` and
`--disable-extra-siteconfig` options to allow or forbid the definition
of a site-specific configuration script controlled with the
`MODULES_SITECONFIG` environment variable.
These options control the default value of the `g_extrasiteconfig`
variable in `modulecmd.tcl`. If this variable is true (by default),
MODULES_SITECONFIG is looked at the siteconfig sourcing time. Thus the
primary siteconfig.tcl can set the variable to false to ensure the
extra siteconfig is disabled whatever the option passed at ./configure
time.
As a consequence a loaded module cannot be loaded a second time in force
mode. So the check of this situation in conflict procedure is not useful
anymore as the TESTSUITE_ENABLE_SITECONFIG_DEBUG non-regression test.
Separator ';' is used instead of ':' on Windows platform. Add a test
leveraging siteconfig.tcl-1 to check path variable handling on a fake
Windows platform.
Set/get default path variable separator with new getPathSeparator
procedure. This way, global variable g_def_separator is defined after
parsing the siteconfig.tcl.
Adapt defined modulepaths in example testsuite configuration file
(modulerc and .modulespath) depending if versioning installation mode is
enabled or not.
Add 'install-testsiteconfig' make target to setup a dummy siteconfig.tcl
file in install_etcdir. Link that to some of the travis checks to run
testsuite with an existing siteconfig.tcl
