-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inclusion of EIC packages in key4hep-spack #346
Comments
I think we'd be happy to include EIC packages here, just adding one point to the discussion Use of upstream repositoriesIf 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 |
This repo assumes that the |
|
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:
This forms a complete and self-consistent set that allows for full simulation and reconstruction. We will need to add a version of the EIC project detector which will be different from athena-eic, but it makes sense to wait until after a name has been chosen...
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.
The text was updated successfully, but these errors were encountered: