https://pantsbuild.org/ logo
Join Slack
Powered by
<@U01PZK60W2F>: it looks like there is an un-publi...
# development
w
@curved-television-6568: it looks like there is an un-published page about `experimental_shell_command`: https://dash.readme.com/project/pants/v2.9/docs/run-shell-commands … is that waiting on something?
c
It's a draft. Would be good to do some proof reading, then it's probably ok to publish, if it looks ok overall.
w
looks good to me! … want me to make it visible for 2.9?
c
Ok by me :)
w
cool: now visible!
👍 1
c
I'll take a look at filling in the missing section at the end of that page later this week..
👍 1
w
i just filled in a few more details here, and reorganized the page a bit
❤️ 1
c
This is not clear to me:
it must be a root target in your build graph
w
um, yea… that’s a fuzzy concept, i suppose.
but it’s not packageable, right? so there is no use in depending on it from any other target
./pants run
works, but 
./pants package
cannot/should-not
➕ 1
c
Yea, no point in depending on it.
w
hence, root. it’s a pretty informal concept though… because we’ve called 
pex_binary
a root in the past (no other python code can/should depend on it)… but a 
docker_image
can depend on it
(…and even 
python_tests
can now, iirc)
c
Ah, right.. that makes sense, but the word 
root
in my mind associates more with a directory than the dependency graph of targets (still!)
so I tried to grok why it had to be in the build root 😛 (feeling I had the wrong idea..)
w
ah, yes… true.
i’d really, really love to formalize the concept of a build graph root. but the changes around 
pex_binary
demonstrate that that is hard
c
so until then, perhaps add a few more words, clarifying the effects of being a root target? 🙂
w
i think that it amounts to:
Copy code
it must be a root target in your build graph (i.e. it may not be consumed by other targets).
👍 1
will edit.
c
yep, that does it. thanks 🙂
Open in Slack
PreviousNext
Powered by