Skip to content

What is a top-level configuration without flake-parts? #561

@sshine

Description

@sshine

Hello,

I've been running dendritic flakes using import-tree + flake-parts for several months, and it's very satisfying. I want to explore alternatives to flakes like unflake, but I think it means I'll lose flake-parts. @mightyiam points out several times that "a top-level configuration" doesn't have to be a flake-parts module; the idea just happened to get invented with this stack.

I found the word "flakeless-parts" in some source code, but it doesn't appear to be a project in itself. I think the power of flake-parts is standardizing on a schema: I spent the most time looking at all these researchy dendritic patterns trying to understand what everyone is doing, since it all looks different. Refreshing, but time-consuming.

So: Is there a flake-parts compatible top-level configuration spec that doesn't require the experimental flake runtime? Or does every non-flake dendritic Nix user rely on their own idea of a top-level configuration?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions