Any chance we’d be able to install specific versions of the

scie-pants

launcher binary via

brew

in the future? I see that such a thing is supported by

get-pants.sh

but not the

brew

installer. We’d like to be able to pin to a version for our organization and do explicit upgrades so that all engineers are on the same version of consistency. Something like this?

brew install pants@0.10.3

I have very little brew knowledge, but feel free to contribute this if you know how it can be made to work. See here for where we update the keg or cask or whatever it's called.

I also have very little brew knowledge 😅

As with all open-source projects - it's down to someone motivated enough to contribute...

> Also, I should emphasize that the launcher binary is not related to the Pants version, which is determined by the version in pants.toml in each repo Yes, this part I’m aware! Mainly want to just minimize as many differences as possible across developer machines. In the past we’ve had issues with different

pyenv

versions even though that’s only the tool used to install Python versions, and not run them. I’ll look into the

brew

thing if I get a chance; otherwise there’s a workaround I can do using the

get-pants.sh

script directly. Thanks! 🙂

Don’t quote me on this, but I think it’s something along the lines of

brew install cask [url]

where

url

is the associated ruby file on GitHub for the commit version you wanted

I’ll try it out! Thanks :)

I’d also bet if you really wanted to, you could vendor the ruby file (Caskfile? I can never keep track of what they call it) and brew install pointed to that local file?

yea, brew is not hot on letting you pick arbitrary versions. So you need to point out a specific cask to install to get that (like SJ suggests) either by a fixed URL or if you fork our tap that’s easy enough to choose when you upgrade it at your own time.