Wouter Deconinck
Wouter Deconinck
> I was taking a look over this and ran into a couple issues. > > 1. The current DIRC_geo code puts the sensitive surface onto the MCP box (https://github.com/eic/epic/blob/main/src/DIRC_geo.cpp#L227C1-L227C93),...
> > Looks good to me. Have not done a one to one comparison with capybara. > > What was the problem with publishing the capybara here as is done...
Builds of `acts@:35` fail with `podio@1` without patching CMakeLists.txt, https://github.com/acts-project/acts/blob/v35.2.0/CMakeLists.txt#L207. Since a newer compatible version is available, I suggest we don't add those patches. Builds of `acts@35:36` cannot use external...
Following up on the `dfelibs` dependency, it does seem that we may need to disable the automatic system `dfelibs` that derives from `ACTS_USE_SYSTEM_LIBS` with: ```diff diff --git a/var/spack/repos/builtin/packages/acts/package.py b/var/spack/repos/builtin/packages/acts/package.py index...
> Should I resubmit the patch just including the DFELIBS changes ? If you mean the suggestion in https://github.com/spack/spack/pull/46010#issuecomment-2308903475, then I think a new PR is perfectly fine as well...
> * the `compiler-wrapper` dependency happens to have the same dag hash as the "missing" `compiler-wrapper` package in the upstream db I think this is more than it just "happens"...
FYI, @rscohn2 Other ordering preferred? Chose to keep 'legacy' first in case this leads to subtle packaging bugs.
@spackbot run pipeline
@spackbot help
FYI @mcarbonneaux