mesa +osmesa

After investigating this for Alexander and comparing with my local build, I'm wondering if mesa +osmesa can resolve #52 (closed). I'm going to put this MR here so I can see if it starts building llvm, which we don't want...

assigned to @wdconinc

changed the description

Next try: mesa@21.2.4

added 2 commits

• a050dad0 - 1 commit from branch master
• f5370838 - mesa +osmesa

Compare with previous version

Maybe we can try installing the missing dependencies with apt and then just direct space to use that version.

added 1 commit

• 1c168513 - Update mesa to latest in spack/develop

Compare with previous version

If this works with the new mesa (which is at the spack/develop hash that we are using), then I propose we get rid of the local version which does not appear to have content that is unique to our setup.

resolved all threads

added 1 commit

• eb00d908 - Delete mesa/package.py

Compare with previous version

@sly2j ready for merge?

Does it work?

merged

Not pulled the mr container to test. But I don't really have time to test it anyway...

The MR is an improvement in any case, so I merged it :)