I've been thinking a lot about resolves and lockfi...
# developmentl
late-advantage-75311
11/02/2023, 12:55 PMI've been thinking a lot about resolves and lockfiles these days. Does anyone have close at hand some of the documents or discussions around resolves and lockfiles from circa the time they were implemented?
c
curved-television-6568
11/02/2023, 3:17 PMI’ll see what I can dig up, my first hit was this one:
https://docs.google.com/document/d/1HAvpSNvNAHreFfvTAXavZGka-A3WWvPuH0sMjGUCo48/edit#heading=h.n451mfzergzm
curved-television-6568
11/02/2023, 3:19 PMand this, I hope it’s accessible?
https://docs.google.com/document/d/1bCYb0UQZx9a-9tAagydCN_z3826QRvz_3aVnXKSNTJw/edit#heading=h.8s9vfj4can9f
curved-television-6568
11/02/2023, 3:21 PMregarding discussions, it ought to be in the slack history. not the most accessible to find all the relevant discussions perhaps. But you’d probably want to focus on discussions involving @hundreds-father-404 as they implemented the lockfile support in pants.
w
witty-crayon-22786
11/06/2023, 9:01 PMhttps://docs.google.com/document/d/1sr1O7W9517w8YbdzfE56xvDb72LafK94Fwxm0juIRFc/edit was the motivating document for multiple resolves, IIRC
witty-crayon-22786
11/06/2023, 9:04 PMthe docs that Andreas linked to are obviously closer to how the configuration ended up: rather than walking into transitive deps to figure out which resolve something is in, they are configured per-target, and each one is a separate universe from a dep-resolution perspective.
l
late-advantage-75311
11/06/2023, 9:55 PMthank you!
late-advantage-75311
11/06/2023, 10:01 PMI am interested in how
Root targets (tests, binaries, published libraries) would each be associated (possibly via a repo-wide default) with a named resolveevolved into also associating resolves with the non-root targets (like python_source and python_requirement). Perhaps it is to be found elsewhere. I am happy to browse the relevant google drive if I have access to read it.
5 Views