spack VS nixGL

> Are we talking about the same autotools?

Yes. Instead of figuring out how to do something particular with every single software package, I can do a --with-foo or --without-bar or --prefix=/opt/baz-1.2.3, and be fairly confident that it will work the way I want.

Certainly with package managers or (FreeBSD) Ports a lot is taken care of behind the scenes, but the above would also help the package/port maintainers as well. Lately I've been using Spack for special-needs compiles, but maintainer ease also helps there, but there are still cases one a 'fully manual' compile is still done.

> Suffice it to say, I prefer to work with handwritten makefiles.

Having everyone 'roll their own' system would probably be worse, because any "mysteriously failure" then has to be debugged specially for each project.

Have you tried Spack?

* https://spack.io

* https://spack.readthedocs.io/en/latest/

Well, good luck with that, cause it's broken.

Previous release miscompiled Python [1]

Current release miscompiles bison [2]

[1] https://github.com/spack/spack/issues/38724

[2] https://github.com/spack/spack/issues/37172#issuecomment-181...

gh is available via Homebrew, MacPorts, Conda, Spack, Webi, and as a…

> I can't count the number of times I've seen people say "md5 is fine for use case xyz" where in some counterintuitive way it wasn't fine.

I can count many more times that people told me that md5 was "broken" for file verification when, in fact, it never has been.

My main gripe with the article is that it portrays the entire legal profession as "backwards" and "deeply negligent" when they're not actually doing anything unsafe -- or even likely to be unsafe. And "tech" knows better. Much of tech, it would seem, has no idea about the use cases and why one might be safe or not. They just know something's "broken" -- so, clearly, we should update.

> Just use a safe one, even if you think you "don't need it".

Here's me switching 5,700 or so hashes from md5 to sha256 in 2019: https://github.com/spack/spack/pull/13185

Did I need it? No. Am I "compliant"? Yes.

Really, though, the main tangible benefit was that it saved me having to respond to questions and uninformed criticism from people unnecessarily worried about md5 checksums.

[1] https://github.com/spack/spack/blob/develop/var/spack/repos/...

In Spack [1] we can express all these constraints for the dependency solver, and we also try to always re-cythonize sources. The latter is because bundled cythonized files are sometimes forward incompatible with Python, so it's better to just regenerate those with an up to date cython.

[1] https://github.com/spack/spack/

You want to look at the tools used for HPC systems, these are generally very well tried and tested and can be setup for single machine usage. Remote access - we use ssh, but web interfaces such as Open On Demand exist - https://openondemand.org/. For managing Jobs, Slurm is currently the most popular option - https://slurm.schedmd.com/documentation.html. For a module system (to load software and libraries per user), Spack is a great - https://spack.io/. You might also want to consider containerisation options, https://apptainer.org/ is a good option.

git clone https://github.com/spack/spack.git ./spack/bin/spack install gcc

How can a program accomplish this? by using/doing something like virtualization? emulation? syscall/API translation? e.g. like WINE?

  [1] https://github.com/nix-community/nixGL

Essentially, running stuff that needs GL graphics is a bit funky... There's a workaround called nixGL though.

I think installing Calibre is a good use case for installing Nix (www.nixos.org).

Unfortunately, you might also need https://github.com/guibou/nixGL to run graphical apps under Nix. It's a shell script to use the correct OpenGL library.

Try the NixGL wrapper.

Are you running the Nix package manager on not-NixOS? If so I recall needing NixGL for OpenGL integration.

$ nix-channel --list home-manager https://github.com/nix-community/home-manager/archive/release-22.05.tar.gz nixgl https://github.com/guibou/nixGL/archive/main.tar.gz nixos https://nixos.org/channels/nixos-unstable

Needs a separate program to run GUI applications on non-NixOS systems

IMO the proper solution to this is Nix/Guix, since they have the best of both worlds (sharing libraries where possible, but allowing different versions where needed). Shame that libGL is a mess and as such is difficult to get right in this way, and as such you need hacks like https://github.com/guibou/nixGL for most GUI stuff. That said, people are working on improving the situation.

I get what you mean, but keep in mind that for every distro you're reliant on the community to get nvidia support integrated. Also if you only have few apps that require it, then the nixGL flake is not bad. https://github.com/guibou/nixGL

nix-channel --add https://github.com/guibou/nixGL/archive/main.tar.gz nixgl && nix-channel --update warning: unable to download 'https://cache.nixos.org/v5djb4jw3hg4brdbidqaspin8n8isyq6.narinfo': SSL peer certificate or SSH remote key was not OK (60); retrying in 259 ms these derivations will be built: /nix/store/gm6gq44ivdqgmrsvlsr08d2nqjircgds-nixgl.drv building '/nix/store/gm6gq44ivdqgmrsvlsr08d2nqjircgds-nixgl.drv'... while setting up the build environment: executing '/bin/bash': No such file or directory builder for '/nix/store/gm6gq44ivdqgmrsvlsr08d2nqjircgds-nixgl.drv' failed with exit code 1 error: build of '/nix/store/gm6gq44ivdqgmrsvlsr08d2nqjircgds-nixgl.drv' failed error: program '/usr/bin/nix-build' failed with exit code 100