Re: git: 94e61d8da52e - main - www/caddy: Update to 2.10.1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2025-08-22 at 18:51, ashish@freebsd.org wrote:
> Hi,
>
> Thanks for staying on top of Go, and Caddy.
>
> I believe this version will require Go 1.25[0]. Maybe you're defaulting
to Go 1.25 in your build environment ?
>
>
===================================================================================

> ===> Fetching github.com/caddyserver/caddy/v2 dependencies
> go: downloading go1.25.0 (freebsd/amd64)
> # get https://proxy.golang.org/cel.dev/expr/@v/v0.24.0.mod
> # get
https://proxy.golang.org/cloud.google.com/go/compute/metadata/@v/v0.7.0.mod
>
===================================================================================

>
> References:
> [0] https://github.com/caddyserver/caddy/blob/v2.10.1/go.mod#L3
>
> HTH
> --
> Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116  20B6 C746 CFA9 E74F A4B0
>
> "If I destroy you, what business is it of yours ?" (Dark Forest, Liu
Cixin)

It does, but that's as expected. Go doesn't do "versions" like we're used
to anymore. If there's a version specified in go.mod, that version's stdlib
will be used no matter what. If it's a future version (i.e. a 1.25 port
like caddy on a 1.24 install), it will automatically download the 1.25
stdlib (as you noted above) and link against it. If it's an older version,
it will adjust its stdlib to have only the features and quirks of that
prior version.

In other words, go x can build apps that specify go y, regardless of x <=>
y. For this reason, there's no need for multiple lang/go ports, and in the
future (i.e. when I have time to get to it) we'll remove all versioned
ports and just have a single lang/go port, because it's capable of building
stuff targetting any future or prior go version.

TL;DR-- Yes, it requires go 1.25, but older (and newer!) versions will
still build the same binary using the same stdlib.

Adam

- --
Adam Weinberger
adamw@adamw.org // adamw@FreeBSD.org
-----BEGIN PGP SIGNATURE-----
Version: FlowCrypt Email Encryption 8.5.11
Comment: Seamlessly send and receive encrypted email

wsG5BAEBCgBtBYJoqL5ACZAZp3yYoOSX6UUUAAAAAAAcACBzYWx0QG5vdGF0
aW9ucy5vcGVucGdwanMub3JnD7u6DsEhUkKNrylgc6xkZj77wICZndnGA4Xf
V/8R+pEWIQTL6ydgPaM9GFLXtmIZp3yYoOSX6QAAg38QAIG8iwv3h9NR6rPN
vJJKizUNCSy811RFuppetKmlCdyaiOlusFgmy8YBw7dYwRIm9LSIwnOp2RoI
rodeh3zmaJ6H7TOv3NZERNr0Zo9yoG/Dm4jTmJSiLJeJ+QBaFaZYLDBlG6tG
Xze1wnzIeuxi8/PwmVSiOrELUak4QcMh2F9mBhH1bSZwYjQtWaDNF5CBT6nO
j+PHHyDpkvCtWo/yoGxkkQqGf2pKslUOdDrJLkPqGnu5ycBgcoecPabkWzWd
VQdT0SbHIiQ/XY+cDyl0usYjGLTCs2Eev0fjZ4qHjic3Ac0N3bLYjAnQnEtG
uGXr4m7iHFUqmriQenOR8W68l+pJw+Nfdnc33wt+MWF015LGGwRSvMSs4sZN
VPVYzt+8AOfYBjf1ut6bjtLU7an5EkE4MHZHmbPs/O6IxJ+9wnTzmKcS64aQ
Brk5pRNvD0BrWOptDMu6F8HjRAvmgoSDOFvRJc9OnxoXB9JbO0Nd3O5oNR5J
XpXWVQyKWixcY169q0vuIAvyltSzJwh8UwQaVPjdgnscyOenQeTYrgaJhUe+
lvkvXIo2gWLs3zFNp8gE0XtKLfVlDpl450zwwADc/CtQg15jJG+npmOLmqti
/q0jPp0LLZUqggt127lGosdTXcb5Jxqy5917m1b0TRwSYmjYt3erTezhFKjF
No4X9T5R
=xTC1
-----END PGP SIGNATURE-----