Expose a toplevel attribute that contains all packages desired by cachix #28
Assignees
Labels
compat: backwards
Represents a backwards compatible change. Existing functionality is wholly unaffected by changes.
priority: low
Non-essential issues that are neither affecting functionality nor usability.
type: feature/addition
Marks the request/implementation of a feature addition. Accompany with relevant labels.
Comments
Frontear
added
priority: low
Frontear
added a commit
that referenced
this issue
Jan 2, 2025
This implements the desired goal of #28. There is now a `config.my.toplevel.cachix` attribute that contains any derivations that need to be built. This is done manually and it's very possible I will miss some things of course. I've already gone through everything once by checking for derivations, `symlinkJoin`-s, `mkDerivation`-s, and all fetchers. I'm not too sure if there's a way to iteratively test things I miss, but for now I think I've caught everything.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This would simplify and cleanup the logic of iterating through the
my.*.packagenamespaces and would garner greater flexibility in capturing packages that are outside of this namespace or not in a namespace at all!An implementation detail could look like as follows:
my.toplevel.cachix-pkgsthat is a Nix list of derivationscachix-pushgrabs this output and uses it to push derivations (maybe flake output is made for this)The text was updated successfully, but these errors were encountered: