Build Isolation and Manifests #918
Merged
Conversation
This file contains 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
Operate certain commands in the local env; the others default to global, but can also operate locally with a flag.
✅ Deploy Preview for elastic-ritchie-8f47f9 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This was referenced Sep 23, 2023
Merged
fare
reviewed
Sep 24, 2023
On top of #918 Adds documentation for the drastic changes in gxpkg.
vyzo
added a commit
that referenced
this pull request
Sep 24, 2023
Drastically improves gxpkg:
- Directories:
- update for the new directory format
- add mighty-gerbils as the default directory
- add a `dir` subcommand to manage the user directory, most notably add
new directories saved in `{GERBIL_PATH|~/.gerbil}/pkg/directory-list`
- Dependency Management
- adds a new deps subcommand to manage the dependencies of the current
package/project
- Package Versioning with git tags
- understands the `@tag` suffix in packages to mean "a git checkoutable
thing"
- implements (non strict) semver for choice of package when there is a
version conflict. This is non strict in the sense that it always chooses
the highest version, without putting a minor cap. We have discussed this
behaviour with fare, belmarca and feeley and we concluded that it is
better to put a subpackage `v2` into your package once you are out of
v1. Anyhow, I am happy with what we have now, but we can revisit in the
future.
- Package build isolation and build manifests
- each project is assembled in its own local GERBIL_PATH (unless the
user has explicitly set GERBIL_PATH) to avoid interference from dirty
`~/.gerbil`.
- each build has a manifest that record the exact dependencies at the
time of build.
See #899
See #780
Closes #703
Closes #895
Closes #899
TBD:
- [x] build isolation: #918
- [x] documentation: #919
- [ ] more testing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This addresses the global-vs-local state madness with .gerbil:
When we are in local package context, we create a new local .gerbil to use for the build, which gives us isolation.
We also create manifests for all the individual packages, so that we can get meaningful error reports.
On top of #916.
See also #651