Arch Linux User Repository

@tanj I'm happy to maintain this package if you'd like.

Thanks for the information, I am happy to change to whatever is recommended now by the devs. Because of time constraints due to my current occupation, I am not unfortunately not able to follow the mailing lists.

I second @simon04, there is no reason to force users to remove go in favour of go-pie, especially since the latter is about to die (follow arch-dev-public@ if you're interested). As for the guidelines you mentioned, they've since been updated with new instructions to enable PIE (namely go build -buildmode=pie).

Fair enough, I will add this to the next iteration.

Installing this package doesn't fully install nextdns; it only installs a binary that can be then used for installation (which leave me with some files that don't belong to any package).

You probably want to include the service file with this package too.

cat /etc/systemd/system/nextdns.service 
[Unit]
Description=NextDNS DNS53 to DoH proxy.
ConditionFileIsExecutable=/usr/bin/nextdns
After=network.target
Before=nss-lookup.target
Wants=nss-lookup.target

[Service]
StartLimitInterval=5
StartLimitBurst=10
Environment=SERVICE_RUN_MODE=1
ExecStart=/usr/bin/nextdns run
RestartSec=120
LimitMEMLOCK=infinity

[Install]
WantedBy=multi-user.target

Please read https://wiki.archlinux.org/index.php/Go_package_guidelines for a sensible explanation of why go-pie is preferred.

Why do you require go-pie? The package builds just fine using go, and go-pie provides go.