David Arnold

For contextual awareness following up on various discussions, here is an instance where current optimizations reach their limit, by pigeon-holing a large dependency tree into the layer limit: https://github.com/nlewo/nix2container/issues/27

The input addressed (not contend addressed) nature essentially ties the manifest creation to a particular registry that actually holds the data. For the time being and experimentation, I consider this...

I completely can see where you are coming from. But let me ask you this: What is your philosophy on "blessed paths" as a tool for new users to find...

from `black` a spec could be ```python # fmt: on # fmt: off ``` or branded (:smile:): ```python # ale: on # ale: off ```

In a similar vein, I was also a bit surprised to find `inputs.fenix.packages.x86_64-linux.fromToolchainFile` instead of `fenix.fromToolchainFile`. (it took me literally 1/2 hour to figure that out) EDIT: nvm, I now...

I think the name-spacing by "/" can proove useful in itself and sets a good precedent. I have a sense it will be useful to export `self.overlays` with a flat...

Ah that would break the name spacing of the genuine overlay import. But an alternative could be to filter those out when exporting `packages` (or alternatively when exporting `overlays` —...

I'd also want to add that https://github.com/numtide/flake-utils/blob/master/filterPackages.nix was intended for providing any kind of filtering services to users. I can't remember exactly why I didn't touch flattenTree filtering, I think...

@nrdxp [do stars align here?](https://github.com/nrdxp/nixflk/blob/a0b9f9ffe688c86bfc04c35655d783289e3484ba/flake.nix#L70-L78) (through PR13). I think `nrdxp/nixflk` is a complement use case to look for. Its flake is already quite complex while trying to solve common use...

I'll try to have some conversations about `tryEval` catching or nor catching build errors, first. This is going to be a long hauler. In the current state of `tryEval` it...