Massimiliano Culpo

It's: ```yaml all: require: - '%[email protected]' ``` In Spack v1.0 compiler are modeled as dependencies, and externals _don't have_ dependencies. This means the `%intel` requirement cannot be satisfied on CMake....

You can either require a unique provider for the languages you care about (in which case you need to use the correct package name): ```yaml packages: c: require: - intel-oneapi-compilers-classic...

> Does Spack 1.1+ treat Scenario A and B the same? @harshula No. In Scenario A there is a _strict requirement_ to depend on the `access_intel` toolchain for all the...

I started having a look at this PR, by checking its performance on a few simple benchmarks which _don't_ involve splicing: [radiuss.develop.20241106.csv](https://github.com/user-attachments/files/17663542/radiuss.develop.20241106.csv) [radiuss.pr.20241106.csv](https://github.com/user-attachments/files/17663543/radiuss.pr.20241106.csv)  It's absolutely in line with `develop`,...

@spackbot run pipeline

The issue might have to do with this PR https://github.com/spack/spack/pull/44425 since the `openmpi` package was not updated, and uses some "internal" API calls. If it's worth it, we might add...

Closing, since there has been no activity in a while. Feel free to reopen if you want to continue work on this.

To fix this properly we need to add the concept of "namespace" to the clingo logic program. I'll try to open an issue and reference all the repos related bugs...