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

29 lines
1.3 KiB
Text
Raw Normal View History

Put postmarketOS aports inside pmbootstrap repo Later, the aports folder will probably get split up in its own repository. But right now this is simply convenient.
2017-05-26 20:26:25 +00:00
pkgname=postmarketos-mkinitfs
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
pkgver=0.9.0
pkgrel=0
Remove busybox aport: telnetd is enabled in upstream now Pull request, that got merged: https://github.com/alpinelinux/aports/pull/1092 Please note, that you can't directly upgrade from postmarketOS "busybox-extras" to the upstreamed version. To upgrade properly, do the following: * delete your self-compiled busybox* packages: `sudo rm ~/.local/var/pmbootstrap/packages/armhf/busybox*` * zap all your armhf chroots with: `./pmbootstrap.py zap`
2017-06-07 21:14:24 +00:00
pkgdesc="Tool to generate initramfs images for postmarketOS"
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"
Put postmarketOS aports inside pmbootstrap repo Later, the aports folder will probably get split up in its own repository. But right now this is simply convenient.
2017-05-26 20:26:25 +00:00
# multipath-tools: kpartx
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="busybox-extras lddtree cryptsetup kmod multipath-tools
postmarketos-mkinitfs: Support initramfs compressions other than gzip (!334) The postmarketos initramfs is larger than android initramfs. This causes problems on some devices like htc-ace that have a very small boot partition (4MB in htc-ace). I've been able to make the boot image small enough to fit by compressing initramfs using lzma. With this change it should be possible to change the compression in deviceinfo like this: deviceinfo_initfs_compression='lzma' or even deviceinfo_initfs_compression='lzma -9'. When no option is specified it defaults to 'gzip -1'. I've also added dependencies to compression utilities for all possible initramfs compression algorithms.
2019-04-30 17:12:33 +00:00
device-mapper parted e2fsprogs e2fsprogs-extra osk-sdl charging-sdl triggerhappy xz bzip2 lz4"
Fix #76: Rebuild initramfs, when installing a initramfs hook Also shellcheck all *.trigger files from now on in the static code analysis.
2017-06-12 22:55:49 +00:00
triggers="$pkgname.trigger=/etc/postmarketos-mkinitfs/hooks:/usr/share/kernel/*"
Split up initramfs to make it smaller (Close #211) (#257) Huge thank you to @drebrez for his amazing work on this PR! * Add generation of initramfs-extra with additional binaries Extract both initramfs with `pmbootstrap initfs extract` Add new splashscreens for missing partitions/files errors Changes in init script: - use busybox findfs applet to find boot partition - mount boot partion - extract initramfs-extra - show error splashscreens accordingly and loop forever - start usb unlock directly from unlock_root_partition (hook removed) * Print out a text message for serial debugging in case of errors Add initramfs-extra files to `pmbootstrap initfs ls` output * Fix trailing whitespace in comment... * ls: Indicate which initramfs we're looking at / add wiki link I've rewritten the initramfs-development article to reflect the changes made in this PR. It will be a good read for someone who extracted the initramfs and wants to know why we have two files.
2017-07-28 18:51:21 +00:00
source="init.sh.in init_functions.sh mkinitfs.sh"
Put postmarketOS aports inside pmbootstrap repo Later, the aports folder will probably get split up in its own repository. But right now this is simply convenient.
2017-05-26 20:26:25 +00:00
arch="noarch"
license="GPL2"
provides="mkinitfs=0.0.1"
postmarketos-mkinitfs: Handle "deviceinfo_bootimg_qcdt" boolean properly (#914)
2017-11-19 14:25:10 +00:00
options="!check"
Put postmarketOS aports inside pmbootstrap repo Later, the aports folder will probably get split up in its own repository. But right now this is simply convenient.
2017-05-26 20:26:25 +00:00
package() {
mkdir -p "$pkgdir/usr/share/postmarketos-mkinitfs/"
New splash images in mkinitfs (#240) Thanks, Martijn Braam! * Made postmarketos-mkinitfs use postmarketos-splash to generate splash images * Added screen sizes to all deviceinfo files * Bumped pkgrel for all device packages
2017-07-23 12:50:40 +00:00
for file in init.sh.in init_functions.sh; do
Put postmarketOS aports inside pmbootstrap repo Later, the aports folder will probably get split up in its own repository. But right now this is simply convenient.
2017-05-26 20:26:25 +00:00
install -Dm644 "$srcdir/$file" \
"$pkgdir/usr/share/postmarketos-mkinitfs/$file"
done
install -Dm755 "$srcdir/mkinitfs.sh" \
"$pkgdir/sbin/mkinitfs"
mkdir -p "$pkgdir/etc/postmarketos-mkinitfs/hooks/"
}
main/postmarketos-mkinitfs: enable profiling with bootchart (!852) If (a) the kernel command line parameters include PMOS_BOOTCHART2 and (b) /sbin/bootchartd exists (i.e., the bootchart2 package has been installed), run /sbin/bootchartd instead of /sbin/init.
2020-01-02 04:12:20 +00:00
sha512sums="1d49db8a48ad513cc548b8a0ea23cc64518e71c93863155b4e9d2271fb46090506331c03d6955d693c8568c248ecc76b218efe4a6f6bba57c41c5f6d775dc61b init.sh.in
3bcec7b35ced7e87c301f71a892e54aa40983396e2ebaa3c8cbd84c91f711b3ca0e30fbc3104b1a1018ec1af51844ba90a63d380359b51db6242562d21776ed0 init_functions.sh
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
eaad43a846eea96abe1bb876369b0925ab52a141545b13099c634f9422017b5e57f809274ae89c0b53ade1db2c5cc4e96bb9841ad933d68f7664543992e8391b mkinitfs.sh"
Reference in a new issue Copy permalink