Replies: 3 comments 10 replies
-
We’ve thought about this before, specifically about setting some kind of generic I don’t think many people would go to the effort of doing that, but there’s certainly an argument that says we should try and represent the most basic situation for compiling a package, which is what most people who initially try and use it would face, where it would fail without that dependency being installed. I’m not saying we won’t or shouldn’t do it, but I think it’s worth having that discussion again before we make any changes. |
Beta Was this translation helpful? Give feedback.
-
Yep, I figured you'd fenced it off and disabled the code with an environment variable trigger. |
Beta Was this translation helpful? Give feedback.
-
This is implemented as |
Beta Was this translation helpful? Give feedback.
-
It'd be great to be able to set environment variable in .spi.yml somehow - specifically, I've worked around the requirement of needing
jemalloc
for building the benchmark package here:ordo-one/package-benchmark#127
So I'd like to set
BENCHMARK_DISABLE_JEMALLOC=1
when building on macOS for SPI (to get the build matrix work for macOS too).Perhaps there are security implications with that, as a workaround maybe I could ask the above environment to be set for the macOS build machines?
Beta Was this translation helpful? Give feedback.
All reactions