I'm finally investigating what using scie-pants ov...
# general
p
I'm finally investigating what using scie-pants over the in-repo
./pants
script means for me and for the StackStorm project. What do people normally do when transitioning projects? • Remove
./pants
and checking the
get-pants.sh
script into the repo instead • Replace
./pants
with a shim script that calls the
pants
bin on the path, downloading it if needed • Remove
./pants
and just change dev docs to explain how to install scie-pants before doing anything else with the repo • Something else?
g
I did option 1, updated docs, posted on slack to switch. No issues.
p
cool. That’s what I’m leaning towards - though I’m going to fix
~/bin
->
~/.local/bin
in my copy.
b
I did 1, but replaced the
./pants
script with a reminder for devs to update their workflow:
Copy code
#!/usr/bin/env bash

# FIXME: remove this in November 2023 or something, once we don't need the reminder any more
cat 1>&2 <<EOF
This ./pants script is no longer supported, use the pants launcher instead, like:

    pants $@
EOF
exit 1
Speaking of which, I'm gonna go remove it now. It's been long enough.
(We had a small team, so I could easily pester everyone to install the script before doing the switch-over, but on a bigger team I guess a link to installation instructions/dev docs would be good.)
p
Yeah. I can't do much pestering in an open source project. It shouldn't be a big deal because the transition to pants isn't complete though.
👍 1