Arch Linux User Repository

Update for 1.0.3 (new license and conflicts suggestion from comments):

diff --git a/PKGBUILD b/PKGBUILD
index 8becbc0..9fc1152 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,16 +1,15 @@
 # Maintainer: Julien Nicoulaud <julien dot nicoulaud at gmail dot com>

 pkgname=sampler
-pkgver=1.0.2
+pkgver=1.0.3
 pkgrel=1
 pkgdesc='A tool for shell commands execution, visualization and alerting. Configured with a simple YAML file.'
 arch=('i686' 'x86_64' 'armv7h' 'armv6h' 'aarch64')
 url='https://sampler.dev'
-license=('custom:Fair Source License')
+license=('GPL')
 makedepends=('git' 'go-pie' 'alsa-lib')
-conflicts=("${pkgname}-git")
 source=("https://github.com/sqshq/sampler/archive/v${pkgver}.tar.gz")
-sha256sums=('3b5240322ed0f48529af94cecee55900ae05ab776531a2e75337bf99fe8b1ff2')
+md5sums=('9403568307a1c2dcd1dea9a4cd15447c')

 build() {
   cd "${srcdir}/${pkgname}-${pkgver}"
@@ -27,4 +26,3 @@ package() {
   install -Dm755 "${pkgname}" "${pkgdir}/usr/bin/${pkgname}"
   install -Dm644 "LICENSE.md" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE.md"
 }
-

@nicoulaj The license is incorrect. (https://github.com/sqshq/sampler/blob/v1.0.2/LICENSE.md)

@nicoulaj: of course you can leave the "conflicts" in, however, it is not necessary. Package sampler-git will have to include a "provides" and "conflicts" for the sampler package (https://wiki.archlinux.org/index.php/VCS_package_guidelines#Guidelines).

@a-wing: changes applied

@willemw: I get your point but it's just defensive, why not leave it ?

conflicts=("${pkgname}-git")

can be removed, because it is the other way round: sampler-git conflicts with sampler.

Maybe ?

@@ -7,21 +7,19 @@ pkgdesc='A tool for shell commands execution, visualization and alerting. Config
 arch=('i686' 'x86_64' 'armv7h' 'armv6h' 'aarch64')
 url='https://sampler.dev'
 license=('custom:Fair Source License')
-makedepends=('go-pie' 'alsa-lib')
+makedepends=('git' 'go-pie' 'alsa-lib')
 conflicts=("${pkgname}-git")
 source=("https://github.com/sqshq/sampler/archive/v${pkgver}.tar.gz")
 sha256sums=('de9065e76d950166fd5e355b1610a3e0697caa4dc3ee5f2877e9da0cd52fc942')

 build() {
   cd "${srcdir}/${pkgname}-${pkgver}"
-  export GOFLAGS="-gcflags=all=-trimpath=${PWD} -asmflags=all=-trimpath=${PWD} -ldflags=-extldflags=-zrelro -ldflags=-extldflags=-znow"
-  env GO111MODULE=on go build
+  GOFLAGS="-gcflags=all=-trimpath=${PWD} -asmflags=all=-trimpath=${PWD} -ldflags=-extldflags=-zrelro -ldflags=-extldflags=-znow" go build
 }

 check() {
   cd "${srcdir}/${pkgname}-${pkgver}"
-  unset GOFLAGS
-  env GO111MODULE=on go test -v ./...
+  go test -v ./...
 }

@nicoulaj: OK then. (I looked at https://wiki.archlinux.org/index.php/Go and it does not mention go-pie at all.)

@willemw: it's Arch's go packaging guidelines (https://wiki.archlinux.org/index.php/Go_package_guidelines#Building)

This package requires the go package to be uninstalled. Is there a specific reason to use go-pie instead of the standard go (go, go-pie) package?