Skip to content

feat: update build concept page #261

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

Merged
merged 5 commits into from
Jun 20, 2025
Merged

feat: update build concept page #261

merged 5 commits into from
Jun 20, 2025

Conversation

zmitchell
Copy link
Member

@zmitchell zmitchell commented Jun 18, 2025

The second commit contains the actual content changes.

Closes #237

@zmitchell zmitchell added the team-cli Tickets relevant to the flox CLI team label Jun 18, 2025
@floxbot floxbot added the documentation Improvements or additions to documentation label Jun 18, 2025
Copy link

@dcarley dcarley self-assigned this Jun 20, 2025
dcarley added 2 commits June 20, 2025 11:40
Describe why you would choose one over the other and what the trade-offs
are.
Copy link

@@ -79,11 +79,13 @@ Builds can be performed with different levels of "purity", meaning different lev
This is controlled with the `sandbox` option.

By default this option is set to `"off"`, which instructs the Flox CLI to perform the build in the root of the repository with no restrictions on network or filesystem access.
This allows your build to use local caches or intermediate build artifacts that already exist.
This is convenient because it allows your build scripts to work as they do in your development environment, such as using local caches and intermediate build artifacts that already exist.
However, there are less guarantees that the build is reproducible, meaning that both the build script and built package may not work the same way on another machine.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion:

However, that also implies that builds can access files or programs specific to your machine, e.g. config files in $HOME, applications installed system wide, etc. and potentially embed this information in the resulting binary.
This can subsequently hurt the reproducibility of build script and the ability run binaries on other machines where those referenced files do not exist.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I golfed it a tiny bit and added to a separate commit.

@dcarley dcarley merged commit 4e25c8b into build-preview Jun 20, 2025
1 of 2 checks passed
@dcarley dcarley deleted the push-voxxkwwsxylt branch June 20, 2025 11:23
Copy link

zmitchell pushed a commit that referenced this pull request Jun 24, 2025
feat: update build concept page
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation team-cli Tickets relevant to the flox CLI team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants