# Maintainer: yonlu <yj@yellowjacket.app>
pkgname=yellowjacket
# A fallback and the default tag for a manual build; pkgver() below is what
# actually decides the version, from the clone's own git history.  Versions
# restarted at 0.0.1 when releases became automatic (plan 017) — which is a
# *downgrade* from the 1.x packages already in the registry, so pacman offers
# no upgrade and an existing install has to be removed and reinstalled once:
#
#   pacman -R yellowjacket && pacman -S yellowjacket
#
# `epoch=1` would have avoided that for one line, and was declined: an epoch
# can never be removed, and it would put a permanent `1:` in front of every
# version string this package will ever have.
pkgver=0.0.1
pkgrel=1
pkgdesc="Cross-platform desktop music player — local library, MusicBrainz explore & auto-tag"
arch=('x86_64')
url="https://git.ljones.me/yonlu/yellowjacket"
license=('custom')
depends=('webkitgtk-6.0' 'gtk4' 'alsa-lib' 'hicolor-icon-theme')
makedepends=('go>=1.25' 'nodejs>=22' 'pnpm' 'git')
options=('!lto')

# Source is overridable so the same PKGBUILD works two ways:
#   * Manual release build (default): clones the tag over SSH (port 2222).
#       git push origin v$pkgver   # push the tag first
#   * CI build on push to main: the workflow sets these to a local file:// clone
#     at the exact pushed commit, e.g.
#       YJ_GITURL="git+file:///build/yellowjacket" YJ_GITREF="#commit=$SHA"
_giturl="${YJ_GITURL:-git+ssh://git@git.ljones.me:2222/yonlu/yellowjacket.git}"
_gitref="${YJ_GITREF:-#tag=v$pkgver}"
source=("$pkgname::${_giturl}${_gitref}"
        "yellowjacket.desktop")
sha256sums=('SKIP'
            'SKIP')

# Derive the real version from git: a clean tag gives 1.3.0.r0.gHASH, commits
# past a tag give 1.3.0.r<N>.gHASH — monotonic and pacman-friendly, so every
# push to main is a newer version than the last.
pkgver() {
  cd "$srcdir/$pkgname"
  git describe --long --tags --abbrev=7 2>/dev/null \
    | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g' \
    || printf '0.0.0.r%s.g%s' "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
}

prepare() {
  cd "$srcdir/$pkgname"
  export GOPATH="$srcdir/gopath" GOFLAGS="-mod=mod -modcacherw"
  go mod download
}

build() {
  cd "$srcdir/$pkgname"
  export GOPATH="$srcdir/gopath" GOFLAGS="-mod=mod -modcacherw" CGO_ENABLED=1

  local commit
  commit="$(git rev-parse --short HEAD)"

  # `go tool wails3/sqlc/templ` resolve from the tool directives in go.mod, so
  # no extra CLIs are needed. Wails runs the frontend install+build itself.
  #
  # v3's build is a Taskfile tree, and the tasks in it invoke `wails3` by bare
  # name — so the vendored tool has to be on PATH under that name or the build
  # dies at its first sub-task with "wails3: command not found". scripts/toolbin
  # is the shim the Makefile uses for the same reason; see the header there.
  export PATH="$srcdir/$pkgname/scripts/toolbin:$PATH"

  # `wails3 build` has no -ldflags flag of its own (that was v2), so the version
  # stamp goes through the LDFLAGS_EXTRA task variable this repo added to
  # build/linux/Taskfile.yml. -trimpath and -w -s are already in the production
  # task's own flags, which is where -clean's frontend rebuild went too.
  go generate ./...
  go tool wails3 task build \
    LDFLAGS_EXTRA="-X 'main.version=v$pkgver' -X 'main.commit=$commit'"
}

package() {
  cd "$srcdir/$pkgname"

  # v3 writes to bin/, not v2's build/bin/ — build/ is tracked build *assets*
  # now (build/config.yml, the icon, the platform Taskfiles).
  install -Dm755 bin/yellowjacket "$pkgdir/usr/bin/yellowjacket"
  install -Dm644 "$srcdir/yellowjacket.desktop" \
    "$pkgdir/usr/share/applications/yellowjacket.desktop"

  # No real logo ships in the repo yet; reuse an in-app SVG as the menu icon.
  # Swap this for a proper branded icon when one exists.
  install -Dm644 frontend/src/assets/images/icons/music/compact-disc.svg \
    "$pkgdir/usr/share/icons/hicolor/scalable/apps/yellowjacket.svg"
}
