Arch Linux User Repository

(preface: I know little about Go) It looks like Arch changed, when you attempt to install go-pie it now triggers the install of go causing this PKGBUILD to fail on it's makedepends(). I dug up in the wiki (and found a go/go-pie bug to match) that now you add -buildmode=pie to your recipe instead. https://wiki.archlinux.org/index.php/Go_package_guidelines

Making these two changes (remove makedepends, adding -buildmode=pie) seems to have produced a working binary for me. https://bugs.archlinux.org/task/60928 is where I found them talking about this change.

Thanks for the patch, @yochananmarqos.

Also, sorry it took me so long to update this. Starting at 0.28.0-1, the PKGBUILD should now properly overload the build version and date (until this point, wtfutil -v just printed dev (dev). Now it should properly output $pkgver (${build date}).

Please add the README, CHANGELOG and sample configs:

package(){
    cd "wtf-$pkgver"
    install -Dm755 "$pkgname" -t "$pkgdir/usr/bin"
    install -Dm644 LICENSE.md -t "$pkgdir/usr/share/licenses/$pkgname"
    install -Dm644 README.md CHANGELOG.md -t "$pkgdir/usr/share/doc/$pkgname"
    cp -r _sample_configs "$pkgdir/usr/share/doc/$pkgname/sample_configs"
}

OK, thanks for the explanation.

@dangersalad: According to Arch's Go packages guideline [1]:

"There are two go packages in the repositories that you can build towards; go and go-pie. All packages should preferably be built towards go-pie as this enables us to deliver secure binaries. However, as upstream might have bugs, building towards go should be a last resort."

I do realize that's mostly aimed at the prebuilt packages at the official repositories, but I figured it'd be good practice to to the same here at AUR. Am I wrong?

[1] https://wiki.archlinux.org/index.php/Go_package_guidelines

Is there a reason to change from go to go-pie?

@matthias.lisin Oh ok, yea, manjaro hasn't caught up yet. When it does, I'll test and report back