Many easyconfigs require the person installing to have extra knowledge. Typical examples include pre-requisites, such as name of the tarball in case it needs to be put in place.
Another current example are the SciPY/Numpy configs. These extensions are currently included in the Python packages and only in special cases would one need to run these separate easyconfigs.
My first proposal (for discussion):
One could provide a field install-infoin the config. One could then have an eb option to print this or have dry-run print this info (if the amount of info is managable). Alternatively one could modify dry-run to signal if packages are to be installed that provide install-info.
Many easyconfigs require the person installing to have extra knowledge. Typical examples include pre-requisites, such as name of the tarball in case it needs to be put in place.
Another current example are the SciPY/Numpy configs. These extensions are currently included in the Python packages and only in special cases would one need to run these separate easyconfigs.
My first proposal (for discussion):
One could provide a field
install-infoin the config. One could then have an eb option to print this or have dry-run print this info (if the amount of info is managable). Alternatively one could modify dry-run to signal if packages are to be installed that provideinstall-info.