multipass: 1.14.0 -> 1.15.0

[jnsgruk]

This commit is a fairly big one:

• Package up the new 1.15.0-rc4 release
• Include the Flutter desktop application
• Move to pkgs/by-name

I've pushed this a little early while we're still in the late rc phase of the Multipass release to get feedback on the restructuring. I noted the following in the commit that introduces the GUI element:

This commit breaks down multipass into two intermediate packages,
`multipassd` and `multipass-gui`. These are then packaged up with
`symlinkJoin` to work around some intricacies in the
`buildFlutterApplication` process which would otherwise be difficult
to patch.

The multipass repo is setup upstream such that the flutter app would
be built as part of the regular cmake process, but that can't work
here due to the fetching of the flutter dependencies. The upstream
multipass project builds `libdart_ffi.so`, which is needed in the
LD_LIBRARY_PATH of the GUI. Building the two derivations seperately
enables that to be done relatively simply.

Hopefully that makes sense! Tested locally on my machine and all works as expected.

Perhaps @RossComputerGuy could give some feedback on this approach, seems they have lots of involvement with the Flutter tooling in nixpkgs.

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.

[getchoo]

Also is there a reason to be updating to a release candidate instead of waiting for a stable release?

[jnsgruk]

Also is there a reason to be updating to a release candidate instead of waiting for a stable release?

Thanks for the feedback, I'll make those changes today - and nice tip on the desktop file, i'd not spotted that before.

Indeed my intention was to wait until the 1.15.0 release, I meant to mark this as draft while i got feedback on the approach 🤦‍♂️

[jnsgruk]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 363626

---

x86_64-linux

✅ 1 package built:

• multipass

[jnsgruk]

@SuperSandro2000 @getchoo feedback addressed, and also now bumped to the actual release, not the RC. Hopefully good to go now! Thanks for the help.

[jnsgruk]

And some screenshots 😄

[jnsgruk]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 363626

---

x86_64-linux

✅ 1 package built:

• multipass

[getchoo]

Diff LGTM, but I'm not all that familiar with flutter

[ambroisie]

I think as it is, this is broken for cross-compilation? And needs to use either:

• $(which protoc-gen-dart) in the shell to look up the nativeBuildInputs.
• ${lib.getExe buildPackages.protoc-gen-dart} in Nix to correctly use a build package, not a host package.