Adrian Schröter writes:
On Freitag, 19. Januar 2018, 15:16:04 CET wrote Egbert Eich:
Yeah, I didn't want to point to you directly ;)
ah, the shy Egbert ...
You mean the use-for-build flags? I was under the *assumption* that hdf5 has them set. It would explain why things break for the HPC flavors of the netcdf build: the hdf5.1.8 package doesn't generate these flavors as the package has not been converted.
no, they were set to use only the 1.8 version.
This was (also?) be done since 1.10 has a different on disk format. While it should still be able to read 1.8 it will break the workflow for people who share the their files (as FreeCAD users).
FreeCAD doesn't look like the classic HPC application while HDF5 is specifically targetting the problems of HPC users and environments - storing very large files on cluster file systems. These problems arise because this file format library is used for use cases it was never intended for :/
I really should have written down the reason for the 5-1.8 package in the package description, but I didn't :/
So, I will reconfigure it to use the 5-1.10 version now to see what was the reason behind (most likely opencascade & FreeCAD).
We do have hdf5 1.10.1 in Factory only, so anyone needing to build against hdf5 and is available in Factory would do so already.
k, will keep an eye on the project. 5-1.8 is currently disabled and not used, just not dropped yet ...
As I said, we can keep it, but the package should be renamed (and packages that depend on it should explicitely use this package name to make sure they get the 'stable' version).