Simon Žlender

Alternatively, add `devenv..{packages,services,tasks,...}` and allow composing setups through the module system and `imports`. For example: ``` devenv.default = { imports = [ config.outputs.frontendModule config.outputs.backendModule ]; }; devenv.frontend = { imports...

Actually, do we even need an explicit `--profile` at all? Can't we just let Nix do its thing?

My understanding is: 1. Nix prefers XDG dirs (not sure since what version, but definitely in 2.18) 2. Nix respects the symlinks `~/.nix-defexpr/channels` and `~/.nix-profile` and will manage profiles wherever...

Actually it's more complicated than that. There's also a `use-xdg-base-directories` option. https://nix.dev/manual/nix/2.22/command-ref/conf-file#conf-use-xdg-base-directories

Either way though, I think hardcoding it to `/nix/var/nix/profiles/per-user/$USER/channels` is wrong if nix is not configured to actually use it. The logic around it is so complex that I would...

> The thing about the pin command that mildly complicates this is it's actually primarily intended to be used as root. Hm, don't we already have conditional logic for root...

> Also, hm, I think that for channels we can't actually make Nix figure it out for us, since it's not actually the default profile (which has software installed in...

Yep, I'm well aware of the `libgit2` mess, and it affects us as well. That's why we're still on 2.18, and given how things are going we'll probably be on...

Try with rust channel `stable` instead of `nixpkgs` (default). The `stable` channel uses fenix which bundles the complete toolchain into a single package.

nix-pkgset no longer generates static/cross variants as it was too convoluted for me to maintain. You could try and generate your own static variant like: ``` foo = nix-pkgset.lib.makePackageSet "foo"...