Yueh-Shun Li

Could anyone take a look at this PR? Cc: @berbiche

@stale This is relevent and awaiting merge.

The tests would be available through the `legacyPackages` output after ~#3024~ #3082 is merged. It can be run automatically by ```console $ nix develop .#tests.run.all ```

It would be more maintainable to rebase onto the master branch instead of making an extra commit to replay the changes on the master branch.

@rrbutani It works! Thanks a lot! It would be helpful to document this as a "way to clean-up" and a workaround of #25.

One more reason for having native macOS support than just use docker: With `nix-portable`, Nix becomes only one executable away from a new user. For example, my friend can try...

@Yajo You can produce the upgraded nix-portable declaratively by overriding the flake inputs.

@nomeata Sorry for late reply. As nix-portable enables the flake features by default, you can make use it to build and run the Nix Flakes. You can find a Flakes...

Another use case: [Nixpkgs](https://github.com/NixOS/nixpkgs) [setup hooks](https://nixos.org/manual/nixpkgs/stable/#ssec-setup-hooks). Nixpkgs is a package repository of Nix package manager, and setup hooks are shell scripts meant to be sourced when building a package. There...

Or, as a workaround, this would also be achievable by supporting a per-file `check-sourced` directive. This way, one can write a meta-script, sourcing the external scripts without checking, and eventually...