bolt-launcher: fix fhsenv version

[Stunkymonkey]

part of #336576

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.

[Stunkymonkey]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 364686

---

x86_64-linux

✅ 1 package built:

• bolt-launcher

[nezia1]

LGTM! For future reference, is pname the standard name that is to be used when packaging derivations in general, or is that mostly for buildFHSEnv?

[Stunkymonkey]

LGTM! For future reference, is pname the standard name that is to be used when packaging derivations in general, or is that mostly for buildFHSEnv?

see: #103997

currently internally it is still used as name = "${pname}-${version}" but parsing version information (needed for updates) from the packages is hard without this split.