Dear Clyde,
It looks like you could potentially benefit from the use of the
'--minimal-toolchains' to EasyBuild. This will by default only build the
required version of the software at the lowest availabel level in the current
toolchain. In this case, you would still end up with 2 versions:
* M4-1.4.17
* M4-1.4.17-GCCcore-5.4.0
This is because the default is to avoid the system GCC except when strictly
necessary (and in this case M4 is a dep of the binutils used to build GCCcore).
There is a further option to include dummy in the minimal toolchain search,
--add-dummy-to-minimal-toolchains, full details can be found at:
http://easybuild.readthedocs.io/en/latest/Manipulating_dependencies.html#using-minimal-toolchains-for-dependencies
Be warned that the utility of this option is dependent on the availability of
the easyconfigs at each appropriate toolchain level. This is increasingly
becoming the case, but is currently not standard practice for many contributors.
Kind regards,
Alan
On Tuesday, 19 September 2017, Clyde Jones
mailto:jones.cl...@gene.com>> wrote:
Hi
When building rpm packages with --package, I get a copy of a package for each
tool chain, plus I need to build the plain package so that dependencies are
resolved.
e.g. for things that require M4 I get the following.
M4-1.4.17
M4-1.4.17-GCCcore-5.4.0
* M4-1.4.17-foss-2016b
* M4-1.4.18
* M4-1.4.18-GCCcore-6.3.0
I'd like to see just
* M4-1.4.17
* M4-1.4.18
What options should I pass to *not* have tool chain as part of the requirements
when building a package, say Python-3.6.1-foss-2017a?
We're currently using HierarchicalMNS for our naming scheme
TIA
--
Clyde Jones
| gRED IT
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
