Silvio Traversaro

> > Just FYI, at my org we obtained good result in caching compilation steps with pixi+colcon with ccache, see [robotology/robotology-superbuild#1920](https://github.com/robotology/robotology-superbuild/pull/1920) (that is not colcon but we also did that...

@mgorny in https://github.com/conda-forge/open62541-feedstock/pull/33#discussion_r1999448301 suggested the right way to fix the problem. The python build dependency should be explicitly set as `python *`, to signal that any version of python is...

> Just for the record, I'm not 100% sure if the current behavior is correct. Same here. If anyone is more aware if this behavior is intended or not and...

Is there any reason for using a different file, instead of adding a section for linux-specific dependencies in the existing `pixi.toml` (after adding `linux-64` to platforms)? I quickly compare the...

Sorry, I had no idea why I added `7zip` in the file, I thought I copied it from your PR, but that was not the case. Do we need `7zip`...

> I think it is possible to only install certain dependencies for certain platforms. I don't remember the syntax, but it is worthwhile looking over the documentation and/or asking about...

Thanks a lot for the work on this! Since I saw https://github.com/wheelnext/nvidia-variant-provider and how it exposed a list of compute capabilities available in the system, I was wondering how that...

Thanks for dealing with this complex problem! Just to understand, a consequence of this is that once fortran and C++ modules start to be adopted, we would need to have...

> The answer (at least based on the solution proposed above) is that you would only need to exchange `{{ compiler("cxx") }}` with `{{ compiler("cxx_modules") }}` in recipes that are...

My bad, I saw the line `- {{ pin_subpackage("gfortran_" ~ cross_target_platform, exact=True) }}` and I tought the version there was the version of the compiler, if that is not the...