aerospace: init at 0.9.0-beta

[t-monaghan]

Description of changes

Introduces aerospace - an i3 like tiling window manager for macOS. I opted to pull from built binaries as the build process is a complex one with some swift dependencies that I couldn't work through after a full days effort. Please let me know if there are any issues with this approach.

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/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 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.

[lolbinarycat]

formatting is a bit unusual, although i can't think of any official guidelines that are being broken for most of it.

[nikitabobko]

I opted to pull from built binaries as the build process is a complex one with some swift dependencies that I couldn't work through after a full days effort

Feel free to describe problems you faced in a new issue https://github.com/nikitabobko/AeroSpace/issues/new The process of building shouldn't be complex. GH actions builds AeroSpace without any problems https://github.com/nikitabobko/AeroSpace/actions/runs/8502224571

But besides the issues with the build setup, building the binary in nix has other flaws. I sign the binary with my private key which is needed to retain macOS accessibility permission across updates (unsigned binaries will re-request the accessibility permission on every update)