Open wdconinc opened 2 years ago
I think we'd be happy to include EIC packages here, just adding one point to the discussion
If existing installations of these packages should continue to be used, it'll probably be easier to keep the eic recipes in their current repository, as spack can be very picky about the namespace the packages were installed from ( even failing with an error when using --reuse
see https://github.com/key4hep/key4hep-spack/issues/344)
This repo assumes that the key4hep
branch of the key4hep/spack fork of spack is used, which is usually somewhat close to develop, and any missing updates from develop can be cherry-picked. I think currently the main differences wrt. develop are a fix for building the nightlies and one for the aformentioned issue concerning --reuse
with upstreams.
Currently in or related to eic-spack , propose to add bold ones to key4hep-spack:
We'd like to start including some of the EIC package in the key4hep-spack repository. This would initially mirror what we have on eic-spack, but due to the integration, we could imagine that eic-spack will start to depend on packages in the key4hep-spack repository.
A few points for discussion.
Targeted set of packages
Initially we would target inclusion of the following set of packages:
Spack target branch
Our packages are currently targeted to Spack develop. That means that they depend on, for example, Acts 18. I think most other packages in key4hep-spack appear to target a different spack version.