packaging: drop the aport; fp6-img installs the published apk
All checks were successful
package / package (push) Successful in 1m55s
All checks were successful
package / package (push) Successful in 1m55s
fp6-img no longer builds imsd from source: its images install the apk this repo's package CI publishes to the registry (pinned version + sha256), so the image and 'apk upgrade' carry the same binary and APKBUILD.binary is the only imsd packaging left. The two payload files the aport carried (kde-modem-daemon skel override, systemd preset) move up to packaging/, where build-package.sh now takes them from.
This commit is contained in:
parent
d5aaf57e49
commit
1987275a54
6 changed files with 10 additions and 90 deletions
|
|
@ -5,10 +5,10 @@
|
|||
# README's "Cross-compiling" section into a proper apk — used by this repo's
|
||||
# package CI (packaging/build-package.sh, which also seds pkgver from
|
||||
# implementations/main.cpp) and runnable by hand. The source tarball is
|
||||
# produced by packaging/make-bin-tarball.sh; the desktop/preset files come
|
||||
# from packaging/aport/ (copy them next to this file). The package payload
|
||||
# must stay identical to packaging/aport/APKBUILD's, or an apk upgrade
|
||||
# across the two pipelines would add/strip files on users' phones.
|
||||
# produced by packaging/make-bin-tarball.sh; the desktop/preset files live
|
||||
# next to it in packaging/ (copy them beside this file). Since 2026-09-02
|
||||
# this is the only imsd packaging: fp6-img images install the apk this
|
||||
# builds from the registry rather than building their own.
|
||||
pkgname=imsd
|
||||
pkgver=0.3.1
|
||||
pkgrel=0
|
||||
|
|
|
|||
Loading…
Reference in a new issue