houdini: 20.5.370 -> 20.5.445

[pedohorse]

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[pedohorse]

Result of nixpkgs-review run on x86_64-linux 1

1 package built:

• houdini

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/prs-ready-for-review/3032/4992

[thiagokokada]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 361799

[wrvsrx]

Why make houdini-runtime as a fixed-output derivation?

[pedohorse]

why fixed-output:
the contents of houdini-runtime is result of self-extraction of installer provided by the vendor. It does not depend on anything except that installer.
When it was not a fixed-output derivation - every time you updated your system you needed to rebuild houdini-runtime from original installer archive, and that archive was being garbage collected all the time - so that all caused a bunch of inconveniences, and took way too much space, since the installer archive is 2+ GB, and houdini-runtime is similarly 2+ GB, and you don't want multiples of them for each system rebuild, especially since they are the same.

but are you experiencing any problems with it being fixed-output now?

[wrvsrx]

I need an older version of houdini. Now I need to set outputHash = null to overrideAttrs.

It doesn't make much inconviniences, but it feels strange to set outputHash for a local build result.

[wrvsrx]

Besides, is houdini running well on your side? I found houdini can't run after #363168. Would you like to check my fix #370461

[pedohorse]

oh my, that's no good.
how come i was not notified about that PR, even though i'm set as maintainer on houdini package??

also for older versions - I'm maintaining this flake, it makes things very easy: https://github.com/pedohorse/houdini-nix
I myself am using only that, so I didn't notice the breakage in nixpkgs