Arch Linux User Repository

@ruifm, I made your suggested changes. Let me know if it works for you.

Could you add 'aarch64' to arch=? I can confirm that it works.

Also, you should replace source_x86_64 by source and sha512sums_x86_64 by sha512sums as the actual source is just source code files and are architecture agnostic.

Could you edit the make && make install line to look like this?

make && make install tags="experimental autopilotrpc signrpc walletrpc chainrpc invoicesrpc routerrpc watchtowerrpc"

The build tags are not well documented by some are needed for keysend to work.

@Spixmaster, Is that right? line 43 sets $GOPATH to "$srcdir".

build() {
  export GOPATH="$srcdir/GOPATH"
  _fake_gopath_pushd "$pkgname" github.com/lightningnetwork/lnd
  make && make install
  _fake_gopath_popd
}

Are you seeing errors when trying to build or the script just looks wrong?

# create a fake go path directory and pushd into it
# $1 real directory
# $2 gopath directory
_fake_gopath_pushd() {
    mkdir -p "$GOPATH/src/${2%/*}"
    rm -f "$GOPATH/src/$2"
    ln -rsT "$1" "$GOPATH/src/$2"
    pushd "$GOPATH/src/$2" >/dev/null || exit
}

There are several lines that do not work because packages only have the permissions to access files in "${pkgdir}". You need to use as a prefix. Especially, the lines above create issues.

The PKGBUILD has the issue that it cannot be reinstalled. First, the yay cache (~/.cache/yay/lnd/) needs to be emptied. Otherwise, this error message appears error cloning lnd: fatal: Zielpfad 'lnd' existiert bereits und ist kein leeres Verzeichnis. which means that the directory "lnd" already exists.

@setpill OK. Thank you for creating the -bin.

FYI I talked to roasbeef on IRC yesterday and he indicated a new release is "a week or two" away. I have also created https://aur.archlinux.org/packages/lnd-bin/ in the interim, and for those who prefer a binary package (signed by upstream).

@setpill, it sounds like this package is in a bit of mess. Go isn't compiling and the gpg keys are expired.

I'll ask the devs about the expired key.

For the Go version, I'll think I'll just wait until upstream fixes. Unless someone gives me a patch to compile with a previous Go version.