home.social

#nixpkg — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nixpkg, aggregated by home.social.

fetched live
  1. 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

  2. #OpenCPN (Chart Plotter #Navigation) 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 search.nixos.org/packages?show

  3. Today's trivial `nixpkgs` bug is github.com/NixOS/nixpkgs/pull/.

    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.

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

    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.

  5. 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.

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

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

  8. 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!