pmaports/device/testing/device-samsung-dream/APKBUILD
Przemysław Romanik d7c036b978
testing/device-many: rebuild to fix wrong initfs-hook.sh location (MR 4187)
postmarketos-mkinitfs!30 and specifically postmarketos-mkinitfs@6fdc8937,
changes expected hooks location from /etc/postmarketos-mkinitfs/hooks
to /etc/mkinitfs/hooks, and another commit pushed later adds
/usr/share/mkinitfs/hooks to expected directories. This more or less
breaks new pmOS installs done by running pmbootstrap install on edge branch,
which pull current (2023-06-17T16:57+02:00) device-* packages from
https://mirror.postmarketos.org/postmarketos/master.
Many of those packages which included initfs-hook.sh no longer work in that
case, because they had those hooks in old location, which isn't used
by latest postmarketos-mkinitfs.

Rebuilding the affected packages solves the issue.

[ci:ignore-count]

[ci:skip-build]: already built successfully in CI
2023-06-19 17:00:28 +02:00

48 lines
1.3 KiB
Text

# Reference: <https://postmarketos.org/devicepkg>
pkgname=device-samsung-dream
pkgdesc="Samsung Galaxy S8/S8+"
pkgver=0.1
pkgrel=6
url="https://postmarketos.org"
license="MIT"
arch="aarch64"
options="!check !archcheck"
depends="postmarketos-base mkbootimg msm-fb-refresher"
makedepends="devicepkg-dev"
source="deviceinfo initfs-hook.sh"
subpackages="
$pkgname-kernel-dreamlte:kernel_dreamlte
$pkgname-kernel-dream2lte:kernel_dream2lte
$pkgname-nonfree-firmware:nonfree_firmware
"
build() {
devicepkg_build $startdir $pkgname
}
package() {
devicepkg_package $startdir $pkgname
}
kernel_dreamlte() {
pkgdesc="Kernel for the Samsung Galaxy S8"
depends="$pkgname linux-samsung-dreamlte"
mkdir "$subpkgdir"
}
kernel_dream2lte() {
pkgdesc="Kernel for the Samsung Galaxy S8+"
depends="$pkgname linux-samsung-dream2lte"
mkdir "$subpkgdir"
}
nonfree_firmware() {
pkgdesc="Non-free firmware for the Samsung Galaxy S8/S8+"
depends="firmware-samsung-dream"
mkdir "$subpkgdir"
}
sha512sums="
04ec398887409ec307a4afb384afcd671fbe9f154f08c6cc65ebaa41bc166d8b948370fe927081abcd50bf5c922cd5df7df2c4c1d8bb8a15b3b8e68a7846a037 deviceinfo
73eb760c6e29c7500b3a2090310f467bb906f7bef2556b80e00e57c25a5fdb1089e86438e67744861a5d43096d8733b812efe39e90a83584816a79d9024a2ec4 initfs-hook.sh
"