I was working on a Spack build for Code_Saturne + Melissa and Spack complained about mismatching hashes when I added GitHub as a "mirror" for the Code_Saturne tarballs.
Please add a warning somewhere that the Code-saturne.org tarball contains a built Doxygen documentation (275+ MB!).
This is implied in the install documentation, though I can make this more explicit.
In versions 6.1 and above, the size of the Doxygen documentation is significantly reduced (simply by switching from .png to .svg file generation options), but is still much larger than a GtHub-generated .tarball.
In any case, if you have Spack build rules you might be interested in sharing, we could put them in the GitHub wiki. Having a community-improved installer would be nice.
In any case, if you have Spack build rules you might be interested in sharing, we could put them in the GitHub wiki. Having a community-improved installer would be nice.
Hi Yvan, as far as I am concerned, the build will be shared with you. Ideally, it should be also be submitted to the Spack maintainers so that it is shipped with their next release but I still need to familiarize myself with Spack.
Yes, that would be nice. It might be interesting to improve the script to include all major dependencies before submitting it to spack maintainers.
Though this also depends how far you want to go. A full build with ParaView + OSMesa, including OSRray one one side, and possibly PETSc on the other (though the latter is useful mainly for CDO models, still WIP, so not urgent) would be great, but might take quite a bit of effort. Unless there are already some Spack rules for this , which would be great. Dependencies such as Melissa are very lightweight and easy to install by comparison...
So it depends on the target, but if this can be improved incrementally, I would be indeed be happy to start somewhere.