https://pantsbuild.org/ logo
#development
Title
# development
c

clever-toothbrush-13797

02/10/2023, 3:53 PM
I don't think I've ever said "hello" here, so: Hello everyone! 👋 I'm considering reviving this PR from a year ago. It introduces
ArchiveSubsystem
that essentially holds search paths for unpacking tools like
unzip
and
tar
. That subsystem should probably go into
core/util_rules/system_binaries.py
. Does anyone have any input on this issue? Does the general approach sound reasonable? Eventually, I'm hoping to make
pants
usable on unmodified NixOS systems where such tools can be put in
PATH
but won't usually be available in the directories listed in the default search path that
pants
uses for bootstrapping. For a preliminary pass on that I would also need to at least give
bash
a similar treatment,. Probably there are other tools that I've forgotten now, as well. I think the relevant issue here would be https://github.com/pantsbuild/pants/issues/14492. Has anything changed about the approach since then?
👋 4
h

happy-kitchen-89482

02/10/2023, 4:59 PM
I think that's still a valid approach, but the relevant options should probably be Environment-aware: https://www.pantsbuild.org/v2.15/docs/environments
New feature since you last looked at this
@ancient-vegetable-10556 your thoughts?
a

ancient-vegetable-10556

02/10/2023, 5:00 PM
👀
on the subject of environment-aware options, yes, that will be necessary if you’re dealing with executable search paths
however, it looks like we moved Archive tools away from their own namespace and into
system_binaries.py
recently. I can’t remember why we did that, but I suspect what we’re really going to want is a way to specify paths for specific binaries rather than just archiving ones
… Sounds like #14492 is indeed the thing that needs to be worked on!
h

hundreds-father-404

02/10/2023, 5:13 PM
I was doing that as prework for this Pr :) centralize binary discovery to one file, and probably one subsystem
3 Views