summaryrefslogtreecommitdiff
path: root/www/ungoogled-chromium/files/patch-ipc_ipc__channel.cc
diff options
context:
space:
mode:
authorAdam Weinberger <adamw@FreeBSD.org>2025-12-05 09:07:28 -0500
committerAdam Weinberger <adamw@FreeBSD.org>2025-12-05 09:07:28 -0500
commitf45b1d07f50b64cebbcd416af8d7ddf265db3de1 (patch)
tree93a6437187240d3799d246ffbb9e896abd65b990 /www/ungoogled-chromium/files/patch-ipc_ipc__channel.cc
parentlang/go12[0-3]: Deprecate; unsupported upstream (diff)
many: Unsupported Go dep; deprecate and schedule for removal
There are about 75 ports that depend on old, unsupported Go versions. I've scheduled those Go versions for deletions on 2025/01/01, and so these ports are scheduled for removal on that same day. HOWEVER.... Likely NONE or VERY VERY FEW of these ports will actually need to be deleted! This stems from a misunderstanding: When go.mod says "go 1.23", it means that it requires AT LEAST go-1.23. Locking a port to a specific go version should almost never happen; it is reserved for when a package absolutely cannot build with any newer version, and it almost means that the port will only last 1 year (Go releases new minors twice a year). Where a port has USES=go:1.23 maintainers should attempt build with just USES=go If that works, please either commit it or submit it in a PR. Same goes go USES=go:1.23,modules to attempt USES=go,modules
Diffstat (limited to 'www/ungoogled-chromium/files/patch-ipc_ipc__channel.cc')
0 files changed, 0 insertions, 0 deletions