irc/soju0.11.1_1

various: Bump Go ports for Go 1.26.10 / 1.27.3

irc/soju: Update to 0.11.1

Changelog:
https://codeberg.org/emersion/soju/releases/tag/v0.11.0
https://codeberg.org/emersion/soju/releases/tag/v0.11.1

Commitlog:
https://codeberg.org/emersion/soju/compare/v0.10.1...v0.11.1

PR:		299308

various: Bump Go ports

many: Bump go ports for 1.26.8 and 1.27.1

various: Bump go ports for go-1.25.14 / 1.26.7

various: Bump go ports for go-1.25.13 / 1.26.6

various: Bump go ports for go-1.25.12 / 1.26.5

various: Bump go ports for go-1.25.11 / go-1.26.4

various: Bump ports for Go 1.25.10

various: Bump go ports for go-1.25.9 / 1.26.2

various: Bump ports for Go 1.25.8

various: Bump ports for Go default 1.24->1.25

various: Bump Go ports for 1.24.13

various: Bump Go ports for 1.24.12

irc/soju: Update to 0.10.1

- Purge extra patches

many: Unpin Go ports

* Ports that were pinned to a deprecated version of Go (1.23 or older)
  have been unpinned.

* Ports that were pinned to a still-supported version of Go (1.24 or
  newer) have been converted to requesting that as their minimum Go
  version.

* Ports that had been forcibly deprecated for pinning an expired Go
  version have been undeprecated.

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

irc/soju: enable syslog output

PR:		289770
MFH:		2025Q4 (decent improvement to have)

irc/soju: add service reload command

PR:		289248

go123 ports: Bump for 1.23.12

irc/soju: Update to 0.9.0

- Depend on Go 1.23

go: Bump ports for go124 update

Bump all go ports for yesterday's releases

irc/soju: Update to 0.8.2

all: Bump after lang/go121 update

irc/soju: Update to 0.8.1

- Point to update upstream

all: Bump after lang/go121 update

all: Bump after lang/go121 update

MFH:		2024Q2

irc/soju: Update to 0.8.0

- strip executables
- add patches for missing constants in PAM headers

irc/soju: enable PAM support and fix build tag addition to GOFLAGS

PR:		279141

all: Bump after lang/go121 update

MFH:		2024Q2

all: Bump after lang/go121 update

MFH:		2024Q2

lang/go: Change DEFAULT to 1.21

PR:		277776
Approved by:	portmgr (exp-run)

irc/soju: Move man pages to share/man

Approved by:	portmgr (blanket)

all: Bump PORTREVISION after lang/go* update

PR:		276530

all: Bump PORTREVISION after lang/go* update

PR:		274405

irc/soju: Update to 0.7.0

all: Bump PORTREVISION after lang/go* update

all: Bump PORTREVISION after lang/go{119,120} update

irc/soju: Update to 0.6.2

irc/soju: Update to 0.6.1

- Switch to using upstream Makefile
- Add rc.d script
- Specify a user/group
- Purge patches which don't apply anymore

PR:		271388

all: Bump PORTREVISION after lang/go{119,120} update

irc/soju: fix build on riscv64

Bump golang.org/x/sys dependency to a version new enough
to support riscv64-freebsd.

Sponsored by:	Berlienr Linux User Group e.V.
Approved by:	portmgr (build fix blanket)

all: Bump PORTREVISION after Go ports update

all: Bump PORTREVISION after lang/go{119,120} update

all: Bump PORTREVISION after GO_DEFAULT update.

all: Bump PORTVERSION after lang/go{118,119} update

all: Bump PORTREVISION after lang/go{118,119} update

all: Bump PORTREVISION after lang/go{118,119} update

irc/soju: Update to 0.5.2