-
Notifications
You must be signed in to change notification settings - Fork 44
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
Support Nix Flakes #546
Comments
- Expose everything as packages, pending to see how we can identify apps
- Expose internals so the CLI can consume them
- Make the CLI compatible with Flakes via a feature flag
- Refactor code so we know what's flake specific - Limit scope of this experimental feature to linux x86-64
I'm just gonna drop here two good reasons not to use flakes yet:
for some companies like us it's not reasonable to risk reliability on production, the thing must just work, preferably for ever on Nix stable this
which means that in a tree like following:
if Maybe this is the reason why some nix experts are using Bazel to achieve incremental builds? We achieved incremental builds at Fluid Attacks using nix stable and I'm gonna stop working towards Flakes for now The work done so far serves as a draft on how compatibility with Flakes can be implemented |
- This merges inputs from the flake and make them available to scripts under the magic makes/ folder as well as to the modules configuration Relates to #540
- It was missing to set the searchPaths
- Assignments involving `self` are only allowed on the right hand side of an output. `evaluatedOutputs` violated this axiom. - Ther reason lies within the recursiveness of these two lines in the builtin flake eval: https://github.com/NixOS/nix/blob/7c90552879da4d1df99b50c85e94201981e60123/src/libexpr/flake/call-flake.nix#L44-L46 fixes: fluidattacks#573
- Assignments involving `self` are only allowed on the right hand side of an output. `evaluatedOutputs` violated this axiom. - Ther reason lies within the recursiveness of these two lines in the builtin flake eval: https://github.com/NixOS/nix/blob/7c90552879da4d1df99b50c85e94201981e60123/src/libexpr/flake/call-flake.nix#L44-L46 fixes: fluidattacks#573
- Assignments involving `self` are only allowed on the right hand side of an output. `evaluatedOutputs` violated this axiom. - Ther reason lies within the recursiveness of these two lines in the builtin flake eval: https://git.io/Jzki9 fixes: fluidattacks#573
- Use the experimental flake support in this repo to help uncover bugs
- Use the experimental flake support in this repo to help uncover bugs
- Use the experimental flake support in this repo to help uncover bugs
- Assignments involving `self` are only allowed on the right hand side of an output. `evaluatedOutputs` violated this axiom. - Ther reason lies within the recursiveness of these two lines in the builtin flake eval: https://git.io/Jzki9 fix: fluidattacks#573
- Use the experimental flake support in this repo to help uncover bugs
- Assignments involving `self` are only allowed on the right hand side of an output. `evaluatedOutputs` violated this axiom. - Ther reason lies within the recursiveness of these two lines in the builtin flake eval: https://git.io/Jzki9 fix: #573
- Use the experimental flake support in this repo to help uncover bugs
- `self.sourceInfo.outPath` brings a string context with it - Drop it for this pattern to work - Idempotent noop in non-flake scenario fixes: fluidattacks#577 (has more context)
- `self.sourceInfo.outPath` brings a string context with it - Drop it for this pattern to work - Idempotent noop in non-flake scenario fixes: fluidattacks#577 (has more context)
- `self.sourceInfo.outPath` brings a string context with it - Drop it for this pattern to work - Idempotent noop in non-flake scenario fixes: fluidattacks#577 (has more context)
- `self.sourceInfo.outPath` brings a string context with it - Drop it for this pattern to work - Idempotent noop in non-flake scenario fixes: #577 (has more context)
- Make inputs now prime over flake inputs - Rename to reflect this special purpose (& temporary) semantics of this arg fixes: fluidattacks#579
- Make inputs now prime over flake inputs - Rename to reflect this special purpose (& temporary) semantics of this arg fixes: fluidattacks#579
- Make inputs now prime over flake inputs - Rename to reflect this special purpose (& temporary) semantics of this arg fixes: #579
Unless I'm mistaken this is fixed the next day by 2143be2, correct? |
Related:
Useful links:
Examples:
Things to take into account:
The text was updated successfully, but these errors were encountered: