* Add cargo-watch
* clippy: the borrowed expression implements the required traits
* clippy: expression creates a reference which is immediately dereferenced by the compiler
* clippy: redundant closure
* clippy: this if-then-else expression returns a bool literal
* clippy: explicit call to .into_iter() in function argument accepting IntoIterator
* Clippy: an implementation of From is preferred since it gives you Into<_> for free where the reverse isn't true
* Support cargo building on a mac
* Create a nix-hook service on macos to inject the shell at startup
* Introduce nix-installe restore-shell to fix the init scripts, called by the nix-hook plist on every login
* Wait for /nix to be there, and restart the hook until it works
* Back to run-at-load hoping that works
* Revert "Back to run-at-load hoping that works"
This reverts commit cccb8bcd971e296fecc0a2dba4f1101795bcd5ba.
It starts too early, fails, and then aborts. When it fails,
launchd says the service failed to initialize and that the system
is read-only.
* nits
* rename to repair
* Handle --no-modify-profile
* fmt
---------
Co-authored-by: Ana Hobden <operator@hoverbear.org>
* Switch to flakehub
* Diagnostics: support user-defined attribution.
Allows a user to specify an additional value to associate their diagnostics with that value. nix-installer doesn't generate or store these values, and most users have no need for it.
* Respond to feedback
* Move Linux only dependencies to isLinux block
SELinux tools are Linux specific
* Add apple_sdk Security framework to devShell
Otherwise cargo build fails with:
ld: framework not found Security
* Add SELinux support
* Nits
* Fix spellcheck
* Don't store mod, use locked shell
* Unwhoops a stale comment
* Speeling: Myy aarch neemesis
* Fix lost code:
* Add method note
* Uninstall shouldn't fail fast
* wip
* wip
* No longer fails fast
* Tidy up error handling
* Touchup post merge
* Refactor nix tests
* Some minor fixes
* Uninstall fail tests
* Fiddle with messaging
* nixfmt
* Tweak display a bit
* fix docs
* Fix Mac
* Revert setting I was testing
* Reflect feedback about a log level
* add some additional vm tests
* Wire things up
* Add further tests
* Fixups
* Add more exhaustive default test check
* Whoops fmt
* Disable a currently breaking test
* Repair notice content in CONTRIBUTING.md