7f8facc9d8
Previously the process was that once a branch is EOL, the
notification-commit was cherry-picked from the branch before.
However that makes less sense, since the package then doesn't go
through the same mass updates as pmaports master does, e.g. it still
referenced gitlab.com & -gtk3, and doesn't allow changes by contributors
other than the one cherry-picking it.
Adapted from c088d806ea25 ("main/postmarketos-upgrade-gtk3: new aport")
See https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/4197.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7769>
25 lines
870 B
Text
25 lines
870 B
Text
maintainer="Achill Gilgenast <achill@achill.org>"
|
|
pkgname=postmarketos-release-upgrade-notification
|
|
pkgver=1.0
|
|
pkgrel=0
|
|
pkgdesc="postmarketOS upgrading notification app"
|
|
url="https://gitlab.postmarketos.org/postmarketOS/postmarketos-release-upgrade-notification"
|
|
arch="all"
|
|
license="GPL-3.0-or-later"
|
|
makedepends="meson libadwaita-dev"
|
|
source="https://gitlab.postmarketos.org/postmarketOS/postmarketos-release-upgrade-notification/-/archive/$pkgver/postmarketos-release-upgrade-notification-$pkgver.tar.gz"
|
|
options="!check" # no tests
|
|
|
|
build() {
|
|
abuild-meson \
|
|
. output
|
|
meson compile -C output
|
|
}
|
|
|
|
package() {
|
|
DESTDIR="$pkgdir" meson install --no-rebuild -C output
|
|
}
|
|
|
|
sha512sums="
|
|
b6bd64030f6cd812a1317ed13810a1140053f2b807dd29bd7248a827506f588ea1681d262e55887194393b69fd2dc7648fc1d8a6fdfc9452d44423c078de3b0e postmarketos-release-upgrade-notification-1.0.tar.gz
|
|
"
|