@polyfloyd that's the idea of #NixOS, which is basically what happens if someone took the ideas of #Flatpak, #Snap and #Docker and consequently made it into the default packaging (#nixpkgs) and deployment (#nixpkg) method for anything beyond the bare minimum OS!

googling for how to update the checksum in a #nixpkg is surprisingly difficult. You get more incorrect solutions than search results.

Why can't you just use a normal sha256 of the exact file downloaded from the url that is literally right above it?

#nix #nixos

#OpenCPN (Chart Plotter #Navigation) https://opencpn.org/index.html

Very cool stuff! I was hoping that something like this was out there, but, I kept hearing references to Navionics and Garmin (ugh!), and never to something open. I am delighted to discover that I won't be limited to proprietary, locked down, software.

There's even a #NixPkg for it https://search.nixos.org/packages?show=opencpn&type=packages&query=opencpn

Backstory, I once submitted Ronin to Kali Linux to be packaged. At first one of their developers accepted the issue and I gave them all of the information on external dependencies and how to install Ronin, etc. I even linked them to gem2deb, a tool that could convert .gem packages into Debian packages, which should have allowed them to package Ronin and all of it's gem dependencies as individual Debian packages. Several months passed without hearing anything back. Then suddenly out of the blue they closed the issue with a vague and rambling excuse about how Ronin hadn't had a release in a while (most of KaliLinux's tools haven't had a release in a while or only have had one release), or that they only package self-contained static binaries (Metasploit is not a self-contained static binary, yet they packaged it). or how they want to save on disk space (Metasploit takes up far more disk space than Ronin, yet they packaged Metasploit). To be fair, I got the impression that they just didn't want to do the work, however I did suspect some kind of double standard was at play here.

Ever since then I began to suspect that KaliLinux is actually holding back the InfoSec community by selectively choosing which tools to package or not to package.

I feel like we need a more decentralized approach to providing a security tools environment. I feel like NixPkg/NixOS can provide that.
#kalilinux #nix #nixpkg #nixos

Today's trivial `nixpkgs` bug is https://github.com/NixOS/nixpkgs/pull/270013#issuecomment-1826668194.

There `sway` attribute type was turned from a derivation into a lambda function. That broke cases where `sway` was augmented with an `.override()` helper. Which is what `nixos/modules/programs/wayland/sway.nix` module does by default.

#nixpkg #bug

Today's minor `nixpkgs` bug is the "excessive" runtime closure size of `meld` package: https://github.com/NixOS/nixpkgs/pull/265454

There `meld` retained development-style dependencies like headers for `libffi` which `meld` should not use (directly or indirectly).

One-liner fix reduced full `meld` runtime closure from 185 to 155 packages. A lot more than I expected.

#nixpkg #bug

So #NixOS on #wsl2 works pretty well, but the VS Code WSL extension keeps breaking for different reasons. I guess the normal Ubuntu WSL distribution with native systemd enabled and #nixpkg multi user installed is the next best thing comparability wise.

Now that I finally feel somewhat confident in writing #nixpkg flakes, I wonder if I'll ever see a need for #Docker files again.

Woo! #ddev #nixpkg is now running through the build tests. Just have the darwin derivatives to complete and the PR should be complete!

Has anyone successfully setup #NixPkg on #Fedora #Silverblue outside of a toolbox container?

#Linux

Gestern habe ich mal #Nix gemacht. #Nvidia 3D samt #Cuda läuft. Schade, das es freie #Photogrammetry mit #Meshroom noch nicht für #NixPkg gibt.

I want to understand #Nix more, and I'm very tempted to "waste" time trying to create a #nixpkg for warp17; but giving that a serious look immediately gives me that familiar feeling of "this would be a difficult first attempt" and that I should probably try to nixpkg something simpler, like say dublin-traceroute (which I also need to package for #OpenBSD)

oh right, FIVE days to finish my EuroBSDcon presentation.

get your head in the game, Glenn!