Should probably amend ropp_svn_install.sh too.

Santi Oliveras adds

Hi all,
When you call build_deps or build_pack, here are the possible options:

grasopr@grassaf3:ropp-8.0> build_deps -h

Purpose: build ROPP dependency packages

Usage:    build_deps <compiler> [package...]

Required: F95 <compiler> tag, e.g. ifort or gfortran

Options:  list of none, one or more supported packages

Default:  netcdf mobufr ecbufr grib

Installs to ROPP_ROOT/<compiler>; saves a a log file in ROPP_ROOT/<compiler>/build_deps.log




grasopr@grassaf3:ropp-8.0> buildpack -h

  buildpack - build latest ROPP module or dependency package

Usage:
  > buildpack package compiler [[NO]CLEAN]
  > buildpack [?|-h|--help]

  Required:
    package  - package name (see Supported packages)
    compiler - Fortran compiler (see Compilers)

  Supported packages:
    NETCDF, MOBUFR, ECBUFR, GRIB, ZLIB, HDF5, NETCDF4,
    ROPP_UTILS, ROPP_IO, ROPP_PP, ROPP_FM, ROPP_1DVAR
    It is recommended to build packages from scratch in the above order,
    except only (at most) one of MOBUFR or ECBUFR need be built.
    Note that GRIB and ZLIB/HDF5/NETCDF4 are also optional.

  Compilers:
    Compiler name matching one of the configuration mini-scripts in
    ./configure : <package>_configure_<compiler>_<os>.
    Examples for <compiler> are:
      ifort, sunf95, nagfor, pgf95, lf95, g95, gfortran, xlf95...

  Options
     CLEAN : remove source directory to re-build from latest archive file
   NOCLEAN : do not clean source directory before a re-build (with the
             same compiler)


It would be great in build_deps an explicid option saying Zlib/HDF5
Netcfd4 full suport or something like that.

Very few (if any) POSIX systems won't have ZLIB as a standard installation (pretty much all Linus distro will have it by default), so the system lib be used. Users will only need to build ZLIB for themselves in rare circumstances, so should not be automatically included in the ROPP dependency build list.

The same goes for HDF5; although this may not be quite so ubiquitous by default, virtually all (Linux) distros will have a pre-built HDF5 in their repositories, and this should be installed if at all possible. Again, it will be rare for users to need to build HDF5 for themselves [unless the distro only has an old version incompatible with the latest netCDF], so should not be in our default list.

In both cases, it is clear in the Release Notes, the scripts' help and in-line comments that the build wrapper script can build these dependencies locally if really necessary (or use the appropriate dependency script or buildpack directly. Ultimately the user is free to add these dependencies to the list within the script if they wish.