> Charlie - what does the -Y flag do for ncra? ie this is the commandline for
> an ncea test which starts out 'ncra -Y ncea'
>
> $test[0]='ncra -Y ncea -O -v one_dmn_rec_var -d time,4 in.nc in.nc foo.nc';
> ^^^^^^^^^^^^
From ChangeLog:
* Add undocumented -Y, --pseudonym, or --prg_nm switch to ncra
to force it to behave as ncea or ncrcat
Using symbolic links in make test ends up being problematic, so we
get around that by always calling the executable by its own name
and not assuming the existence of a symbolic link. This was only
an issue for autotools only. Debian policy, I believe, and common sense, require that 'make check' be capable of running successfully before 'make install' (which creates the symbolic links). So 'make test'
requires a way of testing ncea,ncrcat before symbolic links created,
so we implemented -Y and left it (intentionally) undocumented.
Charlie
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
re-posted from an e-mail:
> Charlie - what does the -Y flag do for ncra? ie this is the commandline for
> an ncea test which starts out 'ncra -Y ncea'
>
> $test[0]='ncra -Y ncea -O -v one_dmn_rec_var -d time,4 in.nc in.nc foo.nc';
> ^^^^^^^^^^^^
From ChangeLog:
* Add undocumented -Y, --pseudonym, or --prg_nm switch to ncra
to force it to behave as ncea or ncrcat
Using symbolic links in make test ends up being problematic, so we
get around that by always calling the executable by its own name
and not assuming the existence of a symbolic link. This was only
an issue for autotools only. Debian policy, I believe, and common sense, require that 'make check' be capable of running successfully before 'make install' (which creates the symbolic links). So 'make test'
requires a way of testing ncea,ncrcat before symbolic links created,
so we implemented -Y and left it (intentionally) undocumented.
Charlie