Do we use the tools we have listed in 3rdparty/too...
# developmentw
wide-midnight-78598
05/23/2025, 12:05 PMDo we use the tools we have listed in 3rdparty/tools in our own repo? I'm digging around, and a bunch of the tools I see in scripts expect system binaries, where we have tool equivalents. The problem being, the tool equivalents are mostly all woefully out of date.
wide-midnight-78598
05/23/2025, 12:08 PMe.g.
ghghacth
happy-kitchen-89482
05/24/2025, 12:37 AMGood question. I don’t know…
happy-kitchen-89482
05/24/2025, 12:37 AMI’m guessing we do not
w
wide-midnight-78598
05/24/2025, 12:40 AMI kinda get the idea of shipping what would otherwise be system installed tools, but on the other hand, I don’t really get it
wide-midnight-78598
05/24/2025, 12:41 AMEven kept up to date, you’re using the version shipped with your version of pants, which feels…. Something
b
broad-processor-92400
05/24/2025, 5:37 AMI think pants itself can likely answer dependency queries… but maybe that doesn’t work for the system binary targets?
Iirc act and gh were added as part of the auto cherry picker work.
broad-processor-92400
05/24/2025, 5:53 AMI think having the repo package ”system” binaries used for internal dev tasks seems pretty reasonable to me, updates not withstanding: if the list of things to install is just scie-pants, and everything else is automatically installed when required, and pinned to known-good versions, seems like much less “works on my machine” and easier for contributors to get started too
6 Views