docs: self-managed comby dev dependency install #6902
Merged
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 updates documentation for installing
comby
as a dependency. There are constraints that make updatingcomby
automatically in the dev scripts hard. These are, roughly:If you are interested in more nitty gritty detail, see the slack thread.
Thus, for development,
comby
will now be a self-managed install, and treated as an external dependency. It is in fact optional unless you work with automation tooling at this point in time. Nothing changes for CI or deployments. There are many options for installing it so that:comby
for development are unaffected (i.e., no broken dev builds, ever, and this is the priority behind this change.)comby
but not the most recent versions can use, e.g.,brew
or grab the binaries from GH and put it on theirPATH
.brew
yet.Test plan: N/A, that's part of the objective.