Adam J. Stewart

@spackbot run pipeline

Build issue reported to https://github.com/iains/gcc-12-branch/issues/10

Now if only scipy didn't also require Fortran...

I'm only maintaining Python/geospatial packages, I'll let someone else review this.

Can you resolve the merge conflicts?

The closest thing we have right now is Spack Environments. That's what I use on my laptop to mimic Homebrew/Conda. It lets me list packages I care about and install...

> fetches `develop` from `origin` Many Spack users who contribute to Spack use `origin` for their own fork and `upstream` for the canonical source. Not sure how to detect which...

Homebrew also uses this same update/upgrade naming scheme, although I always confuse these two commands. But yeah, I would be fine with those names if that's what others want.

Not sure how I feel about this approach. Patching the source code with something that can't be upstreamed is frowned upon, but so is relying on environment variables. I'm inclined...

I tried that once with shapely I think? Basically tried to convince them to use something similar to numpy where the path to the libs is hardcoded in a setup.cfg...