Skip to content

Unify vs flake-aspects vs custom solution #4

@kylebartz

Description

@kylebartz

Currently using flake-parts modules extension to define the modules + classes being used. This has the structure of creating the modules in flake.modules.<class>.<module>. Would instead like a solution that solves the following:

  • Have an explicit set of classes to avoid typos (nixos, homeManager, darwin)
  • classes should be auto-defined for all modules to enable generalized imports/modules lists
  • simplify host definition to have a singular global modules list that applies to nixos + all users (w/ additional user-specific lists)

Some existing options:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions