chore(tools/depotfmt): use Go version from buildGo

This is required because Go 1.18 is actually being deleted. I've
applied the formatting breakage that it introduces (such as breaking
comment formatting), because I can't be bothered to try and work
around broken Go stuff.

Change-Id: Ica7cee0d01228845d6a766079fef36df99a3da96
Reviewed-on: https://cl.tvl.fyi/c/depot/+/9832
Autosubmit: tazjin <tazjin@tvl.su>
Reviewed-by: flokli <flokli@flokli.de>
Tested-by: BuildkiteCI
This commit is contained in:
Vincent Ambo 2023-10-29 13:24:10 +03:00 committed by clbot
parent 6a4b4e37a9
commit 0d880c60b5

View File

@ -11,10 +11,10 @@
//
// # Inputs
//
// * a graph of Nix runtime dependencies, generated via exportReferenceGraph
// * popularity values of each package in the Nix package set (in the form of a
// direct reference count)
// * a maximum number of layers to allocate for the image (the "layer budget")
// - a graph of Nix runtime dependencies, generated via exportReferenceGraph
// - popularity values of each package in the Nix package set (in the form of a
// direct reference count)
// - a maximum number of layers to allocate for the image (the "layer budget")
//
// # Algorithm
//
@ -30,14 +30,15 @@
// │ │
// │ v
// └───> D ───> F
// │
// └────> G
//
// │
// └────> G
//
// Each node (i.e. package) is then visited to determine how important
// it is to separate this node into its own layer, specifically:
//
// 1. Is the node within a certain threshold percentile of absolute
// popularity within all of nixpkgs? (e.g. `glibc`, `openssl`)
// 1. Is the node within a certain threshold percentile of absolute
// popularity within all of nixpkgs? (e.g. `glibc`, `openssl`)
//
// 2. Is the node's runtime closure above a threshold size? (e.g. 100MB)
//