Hi, as some of you may know (Robert Schmidt) we within Compute Canada are in the middle of evaluating various solutions for packaging scientific software for new clusters that are coming online late this year and next year, and I play an important role as one of two software installation coordinators. I'll try to watch remotely some of the user meeting this week (are the sessions also recorded? 4am is a bit early even with small kids) because I am very interested in site experiences.
One of many things we noticed is how the hierarchical module naming scheme is a bit leaky, i.e. you would (and some of us really want to) expect a scheme which purely has modules named packagename/version however there are exceptions, for example: IPython/3.2.1-Python-2.7.10 PyZMQ/14.7.0-Python-2.7.10-zmq4 QuantumESPRESSO/5.2.0-hybrid SuiteSparse/4.4.3-ParMETIS-4.0.3 and the longest name: h5py/2.5.0-Python-2.7.10-HDF5-1.8.15-patch1-serial How would we fix this? Do we make Python part of the toolchains (could even use both python 2 and python 3 as python3 should always work for Python 3.x (see https://www.python.org/dev/peps/pep-0394/)). An extra hierarchy level for HDF5-1.8.15? Or a seperate package name, i.e. h5py/2.5.9 and h5py-serial/2.5.0 ? Of course we can configure all this with Easybuild but have others thought about this or just found it a minor annoyance not to be too worried about? Regards, Bart -- Dr. Bart E. Oldeman | [email protected] | [email protected] Scientific Computing Analyst / Analyste en calcul scientifique McGill HPC Centre / Centre de Calcul Haute Performance de McGill | http://www.hpc.mcgill.ca Calcul Québec | http://www.calculquebec.ca Compute/Calcul Canada | http://www.computecanada.ca Tel/Tél: 514-396-8926 | Fax/Télécopieur: 514-396-8934
