Quentin Smith

Putting it in `activate.custom` means that the checks will run on the remote machine, when you probably want them to run from the machine running `deploy`. Also, in addition to/separate...

What's blocking this PR? Is it just the merge conflicts? It sounds like all that's left for `no_alloc` support is to merge the `rust_max_length` option with `arrayvec` support. (And yes,...

I had a failing `install-flake` check so I dug deep into the logs. First, it's complaining that `/etc/nix/nix.conf` already exists, but that seems to be normal based on looking at...

> In general I tried to keep compatibility with existing modules, however I intentionally excluded activation scripts from the public api for external modules. It would be nice if the...

> I mostly agree with that, since everything is global there is indeed no way to actually prevent this. However currently at least insures that the included module was actually...

> To clarify I'm ok with the changes if they don't remain under the same option as NixOS. For preActivation/postActivation we can use `mkRenamedOptionModule` to provide compatibility. I don't have...

I think a unit smaller than MiB should be used for batch sizes; most common export APIs have limits near the 1 MB mark. For instance, CloudWatch's max batch size...