forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/community/device-generic-x86_64/APKBUILD

63 lines
1.8 KiB
Text
Raw Normal View History

device-generic-x86_64: split off oem-specific packages (MR 4673) This uses oem-specific packages for configuring Intel and AMD systems, and installs them all by default for new images using pmbootstrap's pmb_recommends feature. The intention is to provide pre-built images with support for Intel and AMD already enabled/configured, and users can remove an unwanted set of packages (e.g., `apk del device-generic-x86_64-intel` when on an AMD system) if they want to. Upgrading existing systems should work, in that I haven't observed any apk conflicts with it. But you do need to manually install the new oem-specific package if you need it (e.g. `oem-intel`) fixes https://gitlab.com/postmarketOS/pmaports/-/issues/2484
2023-12-31 07:48:29 +00:00
# Maintainer: Clayton Craft <clayton@craftyguy.net>
device-generic-x86_64: add Ollie as maintainer (MR 5066)
2024-04-26 17:39:40 +00:00
# Co-Maintainer: Oliver Smith <ollieparanoid@postmarketos.org>
device-generic-x86_64: new aport (MR 4554) This device package is intended to replace the tablet-x*uefi device packages. It was made by basically merging config from those two packages. One important change (besides the name, covered later) is that it replaces grub-efi with sd-boot for these devices. The pkgver is starting at '8' to get ahead of the packages this is meant to replace. Because package names, especially for device packages(!), is important, here's a long explanation of why the name is "device-generic-x86_64": "uefi" was excluded from the device package name, because it should (in theory at least...) be able to simultaneously support EFI and non-EFI boot in 1 device package. The device-qemu-amd64 package kiiiinda does this already and could be a useful example for how to do that, though in this situation we'd need to support syslinux for legacy boot instead of what qemu does (bypass installed bootloader and directly boot the kernel). In other words, the packages this one is meant to replace only support EFI boot, they currently don't support legacy boot. So IF we need to support legacy boot in the future and IF there's no way to support both in one package, THEN we can consider changing the name of this one or calling the other "-legacy" or something. "x86_64" instead of "amd64" (like the device-qemu-amd64 device package), because "x86_64" is what Alpine uses to refer to this arch, and it doesn't have a hw vendor name baked into it. "tablet" was dropped from the name, because there are many other x86_64 devices out there that people might want to install pmOS. For example, it might be confusing if you want to install pmOS on an x86_64 toaster but best pmOS image for it is named "device-tablet-..."
2023-10-06 03:07:20 +00:00
pkgname=device-generic-x86_64
pkgdesc="Generic x86_64 system, with EFI"
device-generic-x86_64: various improvements (MR 5066) - Drop -mesa subpackage, this is handled by postmarketos-base now - Add 'quiet' kernel cmdline param to hide kernel messages on boot by default - set chassis type to 'desktop' - re-add firmware-ath6kl, this used to be included in the old tablet-x86uefi but was accidentally dropped when that was merged into this generic device package
2024-04-29 05:15:24 +00:00
pkgver=13
pkgrel=0
device-generic-x86_64: new aport (MR 4554) This device package is intended to replace the tablet-x*uefi device packages. It was made by basically merging config from those two packages. One important change (besides the name, covered later) is that it replaces grub-efi with sd-boot for these devices. The pkgver is starting at '8' to get ahead of the packages this is meant to replace. Because package names, especially for device packages(!), is important, here's a long explanation of why the name is "device-generic-x86_64": "uefi" was excluded from the device package name, because it should (in theory at least...) be able to simultaneously support EFI and non-EFI boot in 1 device package. The device-qemu-amd64 package kiiiinda does this already and could be a useful example for how to do that, though in this situation we'd need to support syslinux for legacy boot instead of what qemu does (bypass installed bootloader and directly boot the kernel). In other words, the packages this one is meant to replace only support EFI boot, they currently don't support legacy boot. So IF we need to support legacy boot in the future and IF there's no way to support both in one package, THEN we can consider changing the name of this one or calling the other "-legacy" or something. "x86_64" instead of "amd64" (like the device-qemu-amd64 device package), because "x86_64" is what Alpine uses to refer to this arch, and it doesn't have a hw vendor name baked into it. "tablet" was dropped from the name, because there are many other x86_64 devices out there that people might want to install pmOS. For example, it might be confusing if you want to install pmOS on an x86_64 toaster but best pmOS image for it is named "device-tablet-..."
2023-10-06 03:07:20 +00:00
url="https://postmarketos.org"
license="MIT"
arch="x86_64"
options="!check !archcheck"
depends="
alsa-ucm-conf
postmarketos-base
systemd-boot
"
makedepends="devicepkg-dev"
source="
deviceinfo
modules-initfs
"
device-generic-x86_64: split off oem-specific packages (MR 4673) This uses oem-specific packages for configuring Intel and AMD systems, and installs them all by default for new images using pmbootstrap's pmb_recommends feature. The intention is to provide pre-built images with support for Intel and AMD already enabled/configured, and users can remove an unwanted set of packages (e.g., `apk del device-generic-x86_64-intel` when on an AMD system) if they want to. Upgrading existing systems should work, in that I haven't observed any apk conflicts with it. But you do need to manually install the new oem-specific package if you need it (e.g. `oem-intel`) fixes https://gitlab.com/postmarketOS/pmaports/-/issues/2484
2023-12-31 07:48:29 +00:00
install="$pkgname.post-install $pkgname.post-upgrade"
device-generic-x86_64: new aport (MR 4554) This device package is intended to replace the tablet-x*uefi device packages. It was made by basically merging config from those two packages. One important change (besides the name, covered later) is that it replaces grub-efi with sd-boot for these devices. The pkgver is starting at '8' to get ahead of the packages this is meant to replace. Because package names, especially for device packages(!), is important, here's a long explanation of why the name is "device-generic-x86_64": "uefi" was excluded from the device package name, because it should (in theory at least...) be able to simultaneously support EFI and non-EFI boot in 1 device package. The device-qemu-amd64 package kiiiinda does this already and could be a useful example for how to do that, though in this situation we'd need to support syslinux for legacy boot instead of what qemu does (bypass installed bootloader and directly boot the kernel). In other words, the packages this one is meant to replace only support EFI boot, they currently don't support legacy boot. So IF we need to support legacy boot in the future and IF there's no way to support both in one package, THEN we can consider changing the name of this one or calling the other "-legacy" or something. "x86_64" instead of "amd64" (like the device-qemu-amd64 device package), because "x86_64" is what Alpine uses to refer to this arch, and it doesn't have a hw vendor name baked into it. "tablet" was dropped from the name, because there are many other x86_64 devices out there that people might want to install pmOS. For example, it might be confusing if you want to install pmOS on an x86_64 toaster but best pmOS image for it is named "device-tablet-..."
2023-10-06 03:07:20 +00:00
subpackages="
$pkgname-kernel-edge:kernel_edge
$pkgname-kernel-lts:kernel_lts
device-generic-x86_64: split off oem-specific packages (MR 4673) This uses oem-specific packages for configuring Intel and AMD systems, and installs them all by default for new images using pmbootstrap's pmb_recommends feature. The intention is to provide pre-built images with support for Intel and AMD already enabled/configured, and users can remove an unwanted set of packages (e.g., `apk del device-generic-x86_64-intel` when on an AMD system) if they want to. Upgrading existing systems should work, in that I haven't observed any apk conflicts with it. But you do need to manually install the new oem-specific package if you need it (e.g. `oem-intel`) fixes https://gitlab.com/postmarketOS/pmaports/-/issues/2484
2023-12-31 07:48:29 +00:00
"
_pmb_recommends="
device-generic-x86_64: various improvements (MR 5066) - Drop -mesa subpackage, this is handled by postmarketos-base now - Add 'quiet' kernel cmdline param to hide kernel messages on boot by default - set chassis type to 'desktop' - re-add firmware-ath6kl, this used to be included in the old tablet-x86uefi but was accidentally dropped when that was merged into this generic device package
2024-04-29 05:15:24 +00:00
firmware-ath6kl
device-generic-x86_64: install all linux-firmware by default (MR 4794) This installs all linux-firmware by default (using pmb_recommends) in a way that allows for users to remove extraneous fw if they want. The old `nonfree-firmware` packages have been dropped since pmbootstrap no longer conditionally installs these. [ci:skip-build]: already built successfully in CI
2024-02-06 12:40:08 +00:00
linux-firmware
device-generic-x86_64: split off oem-specific packages (MR 4673) This uses oem-specific packages for configuring Intel and AMD systems, and installs them all by default for new images using pmbootstrap's pmb_recommends feature. The intention is to provide pre-built images with support for Intel and AMD already enabled/configured, and users can remove an unwanted set of packages (e.g., `apk del device-generic-x86_64-intel` when on an AMD system) if they want to. Upgrading existing systems should work, in that I haven't observed any apk conflicts with it. But you do need to manually install the new oem-specific package if you need it (e.g. `oem-intel`) fixes https://gitlab.com/postmarketOS/pmaports/-/issues/2484
2023-12-31 07:48:29 +00:00
oem-amd
device-generic-x86_64: various improvements (MR 5066) - Drop -mesa subpackage, this is handled by postmarketos-base now - Add 'quiet' kernel cmdline param to hide kernel messages on boot by default - set chassis type to 'desktop' - re-add firmware-ath6kl, this used to be included in the old tablet-x86uefi but was accidentally dropped when that was merged into this generic device package
2024-04-29 05:15:24 +00:00
oem-intel
device-generic-x86_64: split off oem-specific packages (MR 4673) This uses oem-specific packages for configuring Intel and AMD systems, and installs them all by default for new images using pmbootstrap's pmb_recommends feature. The intention is to provide pre-built images with support for Intel and AMD already enabled/configured, and users can remove an unwanted set of packages (e.g., `apk del device-generic-x86_64-intel` when on an AMD system) if they want to. Upgrading existing systems should work, in that I haven't observed any apk conflicts with it. But you do need to manually install the new oem-specific package if you need it (e.g. `oem-intel`) fixes https://gitlab.com/postmarketOS/pmaports/-/issues/2484
2023-12-31 07:48:29 +00:00
"
device-generic-x86_64: new aport (MR 4554) This device package is intended to replace the tablet-x*uefi device packages. It was made by basically merging config from those two packages. One important change (besides the name, covered later) is that it replaces grub-efi with sd-boot for these devices. The pkgver is starting at '8' to get ahead of the packages this is meant to replace. Because package names, especially for device packages(!), is important, here's a long explanation of why the name is "device-generic-x86_64": "uefi" was excluded from the device package name, because it should (in theory at least...) be able to simultaneously support EFI and non-EFI boot in 1 device package. The device-qemu-amd64 package kiiiinda does this already and could be a useful example for how to do that, though in this situation we'd need to support syslinux for legacy boot instead of what qemu does (bypass installed bootloader and directly boot the kernel). In other words, the packages this one is meant to replace only support EFI boot, they currently don't support legacy boot. So IF we need to support legacy boot in the future and IF there's no way to support both in one package, THEN we can consider changing the name of this one or calling the other "-legacy" or something. "x86_64" instead of "amd64" (like the device-qemu-amd64 device package), because "x86_64" is what Alpine uses to refer to this arch, and it doesn't have a hw vendor name baked into it. "tablet" was dropped from the name, because there are many other x86_64 devices out there that people might want to install pmOS. For example, it might be confusing if you want to install pmOS on an x86_64 toaster but best pmOS image for it is named "device-tablet-..."
2023-10-06 03:07:20 +00:00
provides="device-tablet-x64uefi=$pkgver-r$pkgrel device-tablet-x86uefi=$pkgver-r$pkgrel"
replaces="device-tablet-x64uefi device-tablet-x86uefi"
build() {
devicepkg_build $startdir $pkgname
}
package() {
devicepkg_package $startdir $pkgname
}
kernel_edge() {
pkgdesc="Alpine Edge kernel"
provides="device-tablet-x64uefi-kernel-edge=$pkgver-r$pkgrel device-tablet-x86uefi-kernel-edge=$pkgver-r$pkgrel"
replaces="device-tablet-x64uefi-kernel-edge device-tablet-x86uefi-kernel-edge"
depends="linux-edge"
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
}
kernel_lts() {
pkgdesc="Alpine LTS kernel"
provides="device-tablet-x64uefi-kernel-lts=$pkgver-r$pkgrel device-tablet-x86uefi-kernel-lts=$pkgver-r$pkgrel"
replaces="device-tablet-x64uefi-kernel-lts device-tablet-x86uefi-kernel-lts"
depends="linux-lts"
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
}
sha512sums="
device-generic-x86_64: various improvements (MR 5066) - Drop -mesa subpackage, this is handled by postmarketos-base now - Add 'quiet' kernel cmdline param to hide kernel messages on boot by default - set chassis type to 'desktop' - re-add firmware-ath6kl, this used to be included in the old tablet-x86uefi but was accidentally dropped when that was merged into this generic device package
2024-04-29 05:15:24 +00:00
e9dfcd70ccfb9a0fdaa0cdc52faf3be96d6de8af8c60a758bb703c515b0648cec4552e0eaf56e5168b0004cd3fc4b28118abb05dad2c581d3579a2e9134862cb deviceinfo
device-generic-x86_64: initfs: fix FDE w/ usb keyboard (MR 4829) - Fixes FDE unlocking on devices with usb keyboards - Also drops the i915 module from the initfs, this is specified by the oem-intel package now [ci:skip-build] already built successfully in CI
2024-02-13 01:12:06 +00:00
cf9ad3e80b43aa799a8123289e3ab77f6a1c37cee3d48db737688b93afd4f1094db76008ec0f28358c35dd1e115c4fabf9452f9abee76481a2630f02e3ae0953 modules-initfs
device-generic-x86_64: new aport (MR 4554) This device package is intended to replace the tablet-x*uefi device packages. It was made by basically merging config from those two packages. One important change (besides the name, covered later) is that it replaces grub-efi with sd-boot for these devices. The pkgver is starting at '8' to get ahead of the packages this is meant to replace. Because package names, especially for device packages(!), is important, here's a long explanation of why the name is "device-generic-x86_64": "uefi" was excluded from the device package name, because it should (in theory at least...) be able to simultaneously support EFI and non-EFI boot in 1 device package. The device-qemu-amd64 package kiiiinda does this already and could be a useful example for how to do that, though in this situation we'd need to support syslinux for legacy boot instead of what qemu does (bypass installed bootloader and directly boot the kernel). In other words, the packages this one is meant to replace only support EFI boot, they currently don't support legacy boot. So IF we need to support legacy boot in the future and IF there's no way to support both in one package, THEN we can consider changing the name of this one or calling the other "-legacy" or something. "x86_64" instead of "amd64" (like the device-qemu-amd64 device package), because "x86_64" is what Alpine uses to refer to this arch, and it doesn't have a hw vendor name baked into it. "tablet" was dropped from the name, because there are many other x86_64 devices out there that people might want to install pmOS. For example, it might be confusing if you want to install pmOS on an x86_64 toaster but best pmOS image for it is named "device-tablet-..."
2023-10-06 03:07:20 +00:00
"
Reference in a new issue Copy permalink