for the new scie-pants, what’s the right way of ru...
# general
f
for the new scie-pants, what’s the right way of running in a totally segmented env? i can vendor everything in my project, but it’s not clear what all the settings are
c
I don’t understand your question. Are you saying that you had this down before with the pants bootstrap script and need to change anything to make it work with the scie-pants bootstrapper?
f
yep, i need to have it working where essentially all the deps come from the network and none are from internet
it also looks like the BOOTSTRAP_URLS file doesn’t respect relative paths and env variables, so i can’t vendor pants binaries in the repo using pants
things got better updating to 2.18, seems like my existing repos toml was 2.14 so incompatible with ski
is there a way to make bootstrap_urls relative? i’d love to have the c python install only file committed to the repo
c
I’m assuming you mean the
PANTS_BOOTSTRAP_URLS
described here: https://github.com/pantsbuild/scie-pants#firewall-support Have you tried something like?:
Copy code
{
  "ptex": {
    "cpython-3.8.16+20230507-x86_64-unknown-linux-gnu-install_only.tar.gz": "file://./vendor/cpython-3.8.16%2B20230507-x86_64-unknown-linux-gnu-install_only.tar.gz",
     ...
  }
}
f
That didn’t work, “url using bad invalid format”
🫠 1