Arch Linux User Repository

lto were disabled due to debugging issues and compilation errors. If you can test this and confidently say that everything works, I will enable this optimization back.

Regarding the installation of the kernel module - I already wrote that as soon as it appears in the AUR, it will be added to the possible dependencies. To make things easier for you, I will move them to the optdepends block. Regarding the fact that amnezia can now work on the same system as wireguard, I will check today and if this is confirmed, I will remove the conflict.

Another question: Why do you deactivate the build optimizations with !lto?

They both work on one system - I have tried this myself. Did you have any problems with it? Dependencies are not recommendations, so you should be able to install something like that even if it doesn't make sense. Apart from that, it actually makes sense, as you could use the kernel module (one could install it manually) instead of the Go implementation with the tools.

Whitespace and license fixed. Package conflict with wireguard-tools because wireguard and amnezia-wg both have a common code base and they can NOT work in one system. When the situation changes and they can work in one system, I will remove this conflict. The amneziawg-tools package is useless without amneziawg (not yet in AUR due to compilation difficulties) or amneziawg-go, so the dependency is installed. Or do you see a use case for just amneziawg-tools without the core module?

And pkgdesc has a whitespace at the ending. And the description on GitHub is Tools for configuring Amnezia-WG. Without depends:

pkgname=amneziawg-tools
pkgver=1.0.20240213
pkgrel=1
pkgdesc="Tools for configuring Amnezia-WG"
arch=('x86_64')
url="https://github.com/amnezia-vpn/amneziawg-tools"
license=('GPL-2.0 OR MIT')
source=("$pkgname-$pkgver.tar.gz::https://github.com/amnezia-vpn/amneziawg-tools/archive/refs/tags/v$pkgver.tar.gz")
sha512sums=(088448e641256364edb0369b3f23fbfb165a692e4a56e4a8a90cd1812977d70d7bb47f4d5928d167eea035bb5ea1a19372d01919bf8c997167687b7bb3e3d6f5)

build() {
  cd "$pkgname-$pkgver/src"

  make
}

package() {
  cd "$pkgname-$pkgver/src"

  make DESTDIR="$pkgdir" install
}

And the license is also wrong. It is GPL-2.0 OR MIT as SPDX.

Why does it have a conflict with wireguard-tools when it uses a different name?