jaimergp

Hm, have you tried using [`conda-pack`](https://github.com/conda/conda-pack) for the transfer? Sounds like it covers your use case.

> Well, __osx>=12 in the base environment specs did not seem to do anything. That's because the solver runs on the build machine, not the target installation machine. That said...

Giving it a try at https://github.com/conda/constructor/pull/809

Just reporting that as of constructor 3.9.3 and conda-standalone 24.7.1 this feature is supported via `virtual_specs`. See https://github.com/conda-forge/miniforge/pull/626 for inspiration.

CI available at https://github.com/jaimergp/zfp/actions/runs/9568406928/job/26378542726. It passes but I do see some warnings about deprecated APIs: ``` [ 8%] Building C object python/CMakeFiles/zfpy.dir/zfpy.c.o In file included from /opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/numpy/_core/include/numpy/ndarraytypes.h:1909, from /opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/numpy/_core/include/numpy/ndarrayobject.h:12, from...

The workflow triggers are not configured for pull requests. So you have to go to my branch and see the Actions tab there (push event triggers are active).

I can add the PR support here, I think. Then you'll see the button John mentions.

> We actually want this for our feature branches as well, not just develop. I was trying to have the workflows triggered for every push to `develop` (usually a merge),...

Also I'd like to see if you are interested in using Appveyor, given that we can simply configure Github Actions to run on Windows too. Thoughts?

> I'm not sure I understand. Clearly workflows are not triggered currently on PRs, which adding `pull_request` is supposed to address (i.e., what I just did on `develop`). I reverted...