In trying to set up pants in my team's devcontaine...
# general
b
In trying to set up pants in my team's devcontainer I attempted to install it via
bin
, but found that it didn't succeed because
bin
put up an interactive prompt:
Copy code
Multiple matches found, please select one:

 [1] scie-pants-linux-x86_64
 [2] scie-pants-linux-x86_64.sha256
 Select an option:
Is there a better way of reliably installing this? Ideally I'd like to do all the bootstrapping in the devcontainer image instead of each developer having to do it individually (and eat up overlayfs quota)
b
Can you use the
get-pants.sh
script to bootstrap in the image? https://www.pantsbuild.org/2.20/docs/getting-started/installing-pants
Does this
bin
program have options that allow disambiguating non-interactively?
(Depending on what you learn, maybe we can update the
bin
docs there)
c
This is
bin
being broken. For me, it's even worse, as it doesn't consider my current platform, and doesn't even seem to have an option to provide platform info to help guide this..
b
@broad-processor-92400 I'll try that approach next. The rest of my devcontainer config is all declarative in devcontainer.json, and there is a feature that allows installation of binaries via
bin
so that looked attractive compared to running a shell script, but it should be possible nonetheless
I may sort of reverse-engineer what get-pants does specific for this one environment and just manually include its outputs somehow, it's just not super satisfying. I'd love to be able to just include a line in my devcontainer.json and voila pants
oh maybe looking at the github action setup could provide some ideas
having all the devs' codespaces use a shared remote cache would be gravy
c
What it boils down to is downloading the correct binary from the releases on github for the current platform as โ€œpantsโ€.
๐Ÿ‘๐Ÿพ 1
b
yeah and within our codespaces that should be stable + well-defined
๐Ÿ‘ 1