Conversation
The page said Flox would "attempt to produce a build that is compatible with any packages in the 'toplevel' package group", which stopped being true in flox/flox#4708: a Nix expression build now resolves the catalog's current stable revision, or the one named with --stability, and the environment's own packages play no part in it. Say what decides the revision now, and name the consequence that replaces the old compatibility promise — an environment holding both kinds of build builds them against two different package sets, which `flox build` warns about and `flox upgrade` resolves. ECO-59
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
imkarrer
marked this pull request as ready for review
September 18, 2026 16:54
ysndr
approved these changes
Sep 18, 2026
ysndr
left a comment
ysndr
left a comment
Contributor
There was a problem hiding this comment.
Did we change that again?
I still remind that this behavior was specifically targeting a sore experience of not being able to install published software in the same environment on multiple occasions.
That aside, the comment would be correct.
Contributor
Author
|
We havent changed it yet, thats flox/flox#4708. This needs to follow (why dont the docs live with the repo?) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Corrects
concepts/nix-expression-builds.mdx, which told readers that Flox "will attempt to produce a build that is compatible with any packages in the 'toplevel' package group". flox/flox#4708 removes that behaviour: a Nix expression build now resolves the catalog's currentstablenixpkgs, or the revision named with--stability, and the environment's packages play no part in it. Resolves the docs half of ECO-59.The page now says what decides the revision, and names the consequence that replaces the old compatibility promise: an environment containing both manifest and Nix expression builds builds them against two different package sets,
flox buildwarns when they have diverged, andflox upgradebrings them back together.man/flox-build.mdxandman/flox-publish.mdxalso carry the old wording, but they are generated byscripts/sync-man-pages.shfrom flox/flox — the corrected text is in that PR and will arrive with the next sync, so they are deliberately untouched here.Checked with
mint broken-links(the 3 failures it reports are pre-existing/changelog/rss.xmllinks) andvale(clean).