forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/main/devicepkg-dev/APKBUILD

74 lines
3.2 KiB
Text
Raw Normal View History

*: remove quotes around pkgname (MR 1186) TP:[AL3]:APKBUILD:5:pkgname must not be quoted [skip ci]: won't finish within 3 hours
2020-04-25 09:51:42 +00:00
pkgname=devicepkg-dev
main/devicepkg-dev: allow overriding splash config (MR 2931) Allow calling the script with: SPLASH_CONFIG=$srcdir/splash.ini devicepkg_build $startdir $pkgname In order to pass a custom splash config, as it will be used with the PineNote (MR 2910).
2022-02-13 18:39:14 +00:00
pkgver=0.13.2
treewide: fix tabs, final newline, trailing whitespace (MR 3530)
2022-10-14 11:46:40 +00:00
pkgrel=1
Add `devicepkg-dev` which generate the touchscreen udev rule based on the deviceinfo (#995) * Use devicepkg-dev by default in new device wizard * Add link to reference wiki page
2017-12-14 21:17:18 +00:00
pkgdesc="Provides default device package functions"
Remove github.com references * Travis and Coveralls badges * aports: instead of <https://github.com/postmarketOS>, use <https://postmarketos.org> * References to full URLs to issues and pull requests replaced with a hash and the number * grsec check: simplify error message, remove link to github issue (nobody is using that anymore anyway)
2018-06-30 07:00:48 +00:00
url="https://postmarketos.org"
Add `devicepkg-dev` which generate the touchscreen udev rule based on the deviceinfo (#995) * Use devicepkg-dev by default in new device wizard * Add link to reference wiki page
2017-12-14 21:17:18 +00:00
arch="all"
license="MIT"
main/{devicepkg-dev,postmarketos-mkinitfs}: statically generate splash screens (!899) We need to generate the splash screens separately for each device, because they are specific to the device's display resolution. At the moment we do this dynamically during the installation process. This has the advantage that there is no need to re-build all device packages when one of the splash screen is changed (or a new one is added). In reality, however, the splash screens do not change very frequently. On the other hand, generating the splash screens dynamically has signficant disk usage overhead for a minimal ("none" UI) rootfs: The Python interpreter together with the necessary libraries requires about ~60 MB of disk space on aarch64. The splash screens itself require about ~100 KB for 720x1280. This is not necessary if we move the splash screen generation into devicepkg-dev, which is used to build the device package for all devices. Another advantage is that we no longer need the (rather complicated) caching mechanism for splash screens - so we actually end up with less lines than before. rootfs size for samsung-a5ulte ("none" UI): Before: 450M After: 388M (-62M) After this change, every(!) device package needs to be rebuilt once. No changes are necessary in device packages.
2020-01-20 15:30:01 +00:00
depends="postmarketos-splash"
Add `devicepkg-dev` which generate the touchscreen udev rule based on the deviceinfo (#995) * Use devicepkg-dev by default in new device wizard * Add link to reference wiki page
2017-12-14 21:17:18 +00:00
source="
devicepkg-dev: ship compiler-gcc.h for GCC8 We used to put a "compiler-gcc6.h" file inside every vendor kernel's aport. This is redundant and only works with GCC6. With this patch, a common "compiler-gcc.h" file will be used, that works independently of the GCC version. The file is from Decatf's android_kernel_samsung_p4 repository, where it was taken from upstream Linux, but adjusted to work with older vendor kernels (different #ifndef check at the top etc). https://github.com/Decatf/android_kernel_samsung_p4/blob/bd0772df2132bf56cda78e7204facf434cd5aa40/include/linux/compiler-gcc.h
2018-10-05 06:02:52 +00:00
compiler-gcc.h
Add `devicepkg-dev` which generate the touchscreen udev rule based on the deviceinfo (#995) * Use devicepkg-dev by default in new device wizard * Add link to reference wiki page
2017-12-14 21:17:18 +00:00
devicepkg_build.sh
devicepkg_package.sh
devicepkg-dev kernel prepare function
2018-07-02 00:12:49 +00:00
downstreamkernel_prepare.sh
main/devicepkg-dev: add downstreamkernel_package helper (!976)
2019-10-28 17:28:15 +00:00
downstreamkernel_package.sh
Add support to different deviceinfo variables in mainline/downstream subpackages
2018-10-15 19:54:15 +00:00
devicepkg_subpackage_kernel.sh
testdata/deviceinfo
testdata/expected-deviceinfo-downstream
testdata/expected-deviceinfo-mainline
Add `devicepkg-dev` which generate the touchscreen udev rule based on the deviceinfo (#995) * Use devicepkg-dev by default in new device wizard * Add link to reference wiki page
2017-12-14 21:17:18 +00:00
"
Add support to different deviceinfo variables in mainline/downstream subpackages
2018-10-15 19:54:15 +00:00
check() {
# Prepare a temporary dir to run the tests
testdir=$(mktemp -d)
install -Dm644 "$srcdir/deviceinfo" \
"$testdir/src/deviceinfo"
# Execute the script to create the subpackage deviceinfo
sh devicepkg_subpackage_kernel.sh \
$testdir linux-test linux-test-kernel-downstream
sh devicepkg_subpackage_kernel.sh \
$testdir linux-test linux-test-kernel-mainline
# Compare the result with the expected files
if ! cmp -s "$srcdir/expected-deviceinfo-downstream" \
"$testdir/pkg/linux-test-kernel-downstream/etc/deviceinfo"; then
echo "ERROR: unexpected result with downstream deviceinfo"
exit 1
fi
if ! cmp -s "$srcdir/expected-deviceinfo-mainline" \
"$testdir/pkg/linux-test-kernel-mainline/etc/deviceinfo"; then
echo "ERROR: unexpected result with mainline deviceinfo"
exit 1
fi
# Cleanup
rm -r "$testdir"
}
Add `devicepkg-dev` which generate the touchscreen udev rule based on the deviceinfo (#995) * Use devicepkg-dev by default in new device wizard * Add link to reference wiki page
2017-12-14 21:17:18 +00:00
package() {
install -Dm755 "$srcdir/devicepkg_build.sh" \
"$pkgdir/usr/bin/devicepkg_build"
install -Dm755 "$srcdir/devicepkg_package.sh" \
"$pkgdir/usr/bin/devicepkg_package"
devicepkg-dev kernel prepare function
2018-07-02 00:12:49 +00:00
install -Dm755 "$srcdir/downstreamkernel_prepare.sh" \
"$pkgdir/usr/bin/downstreamkernel_prepare"
main/devicepkg-dev: add downstreamkernel_package helper (!976)
2019-10-28 17:28:15 +00:00
install -Dm755 "$srcdir/downstreamkernel_package.sh" \
"$pkgdir/usr/bin/downstreamkernel_package"
Add support to different deviceinfo variables in mainline/downstream subpackages
2018-10-15 19:54:15 +00:00
install -Dm755 "$srcdir/devicepkg_subpackage_kernel.sh" \
"$pkgdir/usr/bin/devicepkg_subpackage_kernel"
devicepkg-dev: ship compiler-gcc.h for GCC8 We used to put a "compiler-gcc6.h" file inside every vendor kernel's aport. This is redundant and only works with GCC6. With this patch, a common "compiler-gcc.h" file will be used, that works independently of the GCC version. The file is from Decatf's android_kernel_samsung_p4 repository, where it was taken from upstream Linux, but adjusted to work with older vendor kernels (different #ifndef check at the top etc). https://github.com/Decatf/android_kernel_samsung_p4/blob/bd0772df2132bf56cda78e7204facf434cd5aa40/include/linux/compiler-gcc.h
2018-10-05 06:02:52 +00:00
install -Dm644 "$srcdir/compiler-gcc.h" \
"$pkgdir/usr/share/devicepkg-dev/compiler-gcc.h"
Add `devicepkg-dev` which generate the touchscreen udev rule based on the deviceinfo (#995) * Use devicepkg-dev by default in new device wizard * Add link to reference wiki page
2017-12-14 21:17:18 +00:00
}
main/devicepkg-dev: don't use kernel 'flavor' in kernel filename (MR 2426) Kernel file names will be generic (/boot/vmlinuz). Release path still has the 'flavor' in it so that pmbootstrap can still get a reference to which kernel package is installed
2021-08-17 23:25:46 +00:00
sha512sums="
d69930dd790b00fb39760a37d95a10899f0d167e10e2804feb05d9ce04f94185dc32d36edc90214aba2ea2aa09bf18f7dab93f1d2eff23f67beb2cc83be30e7c compiler-gcc.h
main/devicepkg-dev: allow overriding splash config (MR 2931) Allow calling the script with: SPLASH_CONFIG=$srcdir/splash.ini devicepkg_build $startdir $pkgname In order to pass a custom splash config, as it will be used with the PineNote (MR 2910).
2022-02-13 18:39:14 +00:00
77dcc7bc4f90bc11f99b7bb88be171f706f7d92921b694ce862d31ab858a4b8850c9e0bdb68299ffce9f934a3c8ab16eb307fd09534085e65f0101334bd68a9d devicepkg_build.sh
main/devicepkg-dev: generate /etc/machine-info (MR 1246)
2020-05-15 17:41:48 +00:00
74c1b9b265a943604d5d538ca66d4b7bcad9adcf40710ab19d795b55aac39669bf1089f7f0ec81aa7a01b537784bef4310e4acc3d7a6ba1f282ab01652bdc4d4 devicepkg_package.sh
treewide: fix tabs, final newline, trailing whitespace (MR 3530)
2022-10-14 11:46:40 +00:00
f81e74e45ae8e55686ae459f550e229e7398daeafa72bd023c2d8c3a0d50e60bf53d5bbdfec931e9fbabe1cd71de57b2192805aaef091ab90bc7203cbaf66ba6 downstreamkernel_prepare.sh
main/devicepkg-dev: don't use kernel 'flavor' in kernel filename (MR 2426) Kernel file names will be generic (/boot/vmlinuz). Release path still has the 'flavor' in it so that pmbootstrap can still get a reference to which kernel package is installed
2021-08-17 23:25:46 +00:00
107242a3da38a574c46cb779e0c75afbeef4cfe659e1b85971973ac55843df06f70f53a5985ca623d4123f05f2984f5dace4a53a3509ecefd7dfdc3c8b705cfe downstreamkernel_package.sh
main/devicepkg-dev: Fix deviceinfo variables for kernels with "-" in name (!892) Kernel subpackages may contain a "-" (e.g. -kernel-mainline-modem); replace it with an underscore to make sure that we find the kernel-specific variables in deviceinfo.
2020-01-18 10:43:16 +00:00
cf5ee240cd1c1e9d30cdec833b4a007fd2e00f9a32ba3f265f99aa2e3dd3601cf43c08d3f3e01bade1d5b2648a6754b2f236e5cb4a9945e18e5c4e97aa2ed7c8 devicepkg_subpackage_kernel.sh
Add support to different deviceinfo variables in mainline/downstream subpackages
2018-10-15 19:54:15 +00:00
9bb7f2a0930f397a713e9f4b6d5b83a426d9a2a3f692dcc42ac30717bf26ead869d8823a38f3ad388af12b2b9a02e8ec4d4418e9c2062389ed06d2b891a49ff3 deviceinfo
136247a16ec91dc0c7241eeddb28c2196ae3b29946a9bc7e9566f848491ef1c53b12d05bf2dbc1cc352986712fd76f25c1510bcc8f301af540a2f01c33b299e1 expected-deviceinfo-downstream
main/devicepkg-dev: don't use kernel 'flavor' in kernel filename (MR 2426) Kernel file names will be generic (/boot/vmlinuz). Release path still has the 'flavor' in it so that pmbootstrap can still get a reference to which kernel package is installed
2021-08-17 23:25:46 +00:00
8cdbf149e1bdfaf4d4a246a208732836956fd81a3aa01ef968e4c2e2cca4027f71cfc38e22debade83ddfca4e05267983c1c8a9c1aa9461a8cf493ef7e893097 expected-deviceinfo-mainline
"
Reference in a new issue Copy permalink