-
-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wip: std skelleton (missing d2n function; help!) #433
base: main
Are you sure you want to change the base?
Conversation
app = { | ||
source = inputs.src; | ||
projects = { | ||
prettier = { | ||
name = "prettier"; | ||
subsystem = "nodejs"; | ||
translator = "yarn-lock"; | ||
}; | ||
}; | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Help, please! 🙏 — This needs to be a derivation
. How would I do that?
}: { | ||
default = cell.packages.app; | ||
app = | ||
# a terrible idea |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could work but completely destroys the harmony 😃
But I don't think this is the right way. There must be a better way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, we do not have a less terrible interface ;)
I plan to re-design this completely
I recently created a collaborative document to discuss how the new drem2nix API should look like.
Feel free to collaborate and dump your ideas there: https://pad.lassul.us/UswFgE39SDuvRcT3R7irNQ?view
To summarize it. I plan to change dream2nix to not provide any functions
itself, and instead only export modules for drv-parts. After this, everything will evolve around individual derivations instead of flakes. Composing multiple packages to something like a flake will then be up to the user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, that is frankly extremely promising.
I engaged in a round of (extensive) comments trying to fully cover my stakeholder perspective as a:
- DevOps persona operating on the intersection of Ops, Build & DevX along the entire SDLC.
- Horizontal Integration Framework maintainer (i.e.
std
) addressing the SDLC wholistically.
I'll reproduce the question about potential output contracts for Standard BlockTypeActions to consume (drv-parts contracts vs d2n contracts) also here in github: DavHau/drv-parts#1
}) | ||
.packages | ||
.${inputs.nixpkgs.system} | ||
.default; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might want to pick prettier
here instead of default. Sometimes the default
might not point to what you want. The heuristic is a bit poor as of now.
No description provided.