I'd like to use

shell_command

to install a tool and have it on

PATH

for a python test. The

shell_command

is working great for hemertically retrieving and unpacking a tar file I need, but I'm not sure how to round out the last part of making sure the proper binary directory shows up on

PATH

in my test execution. Any examples I should go looking for?

Eventually I'd love to be able to have targets represent files AND env vars. But that's probably just me. Can you have your test depend on a Python file that itself depends on your generated tool? Then the python file adds to PATH (or similar)

Yeah, that's what I was thinking about doing. Anyone who would want to use this tool can depend on it coming from this module to hide all those dependency details. Just wanted to make sure there wasn't a more proper way to do that at the BUILD file layer

Wrong thread?

Woops 🙂