Implemented pipeline detection for PGXS and pgrx #12
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.
The PGXS pipeline examines the Makefile (via regular expressions), while the pgrx pipeline examines
Cargo.toml
(via the cargo_toml crate). Each produces a score (0-255), and the highest score wins. If all pipeline candidates return 0 it returns an error. Now Build::new handles a pipeline name specified in the release metadata, while Build::detect figures out which to use when none is specified.Builder::new now takes a
sudo
param, to indicate whethersudo
and passes it to Build::new and Build::detect.Other tweaks:
install
method to the Builder, the Pipeline trait, andplaceholder implementations in the Pgrx and Pgxs implementations.
download
andunpack
methods from the Builder,Pipeline trait, and implementations, as the api::Api struct handles
this functionality.