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

57 lines
1.4 KiB
Text
Raw Normal View History

device/device-qemu-amd64: fix APKBUILD (!874)
2020-01-10 16:45:30 +00:00
# Reference: <https://postmarketos.org/devicepkg>
qemu-*: move from testing to main (!1121) For testing changes for device categorization, it is useful to have a device in each of the categories. The PinePhone is close to being moved to main/, but it doesn't fulfill all requirements yet. The QEMU "device ports" are very simple since QEMU currently only emulates a rather limited set of hardware features. All available features are working correctly (especially after the recent rework of the QEMU packages). I suppose it is also usable as a "daily driver", at least for its intended purpose (a virtual machine for testing postmarketOS changes). :) Given that everyone can run QEMU, everyone could potentially maintain it. For now I have added myself as maintainer since I did most of the recent cleanup. Add drebrez as second maintainer. Overall it seems useful to have qemu-* in main/, especially because it is now the device that is selected by default in pmbootstrap.
2020-04-04 10:30:51 +00:00
# Maintainer: Minecrell <minecrell@minecrell.net>
# Maintainer: Daniele Debernardi <drebrez@gmail.com>
Unified linux-postmarketos kernel for qemu and n900 (#228) The creates the linux-postmarketos package which for now supports the n900 (and probably the other maemo devices) and qemu with the vexpress-a9 machine simulation. I've put the generated dtbs in /usr/share/dtb for now and set the dtb field in the deviceinfo for the n900 and my new qemu device. * Introduced linux-postmarketos-omap * Unified kernel progress * Created kernel bootable with qemu * Updated n900 deviceinfo for generic kernel * Changed qemu device to vexpress * Updated APK comments and added linux-postmarketos-dev package * Append dtb in mkinitfs * Fixed bootscript on n900 for the generic kernel * Don't detect double flavors with -dtb appending * Added graphics drivers for vexpress (qemu) * Added more drivers for qemu This adds virtio network support in qemu for the vexpress-a9 machine. The keyboard and mouse don't work yet. You can boot into weston if --no-fde is specified
2017-07-25 20:08:35 +00:00
pkgname=device-qemu-amd64
qemu-*: cleanup, use consistent hardware (!1029) pmbootstrap now configures consistent QEMU hardware for all architectures. This means that the device package for amd64/aarch64 is now almost identical, except for the architecture and the name of the serial port. pmbootstrap always uses virtio-gpu now (but not necessarily virgl), so there is only one consistent set of initfs modules we need to configure for both architectures. Also add the xfce4 package from amd64 to aarch64, exactly the same problem with the wallpaper exists there.
2020-03-06 13:01:14 +00:00
pkgver=2
pkgrel=0
pkgdesc="Simulated device in QEMU (x86_64)"
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"
device-*: don't use noarch anymore Use the device's architecture instead of noarch. Because the device packages should never be built for other architectures, even if all depends can be built for other arches as well. This simplifies package building as part of the new build infrastructure effort. pmbootstrap has also been changed to output this by default in aportgen.
2018-11-07 06:45:58 +00:00
arch="x86_64"
Unified linux-postmarketos kernel for qemu and n900 (#228) The creates the linux-postmarketos package which for now supports the n900 (and probably the other maemo devices) and qemu with the vexpress-a9 machine simulation. I've put the generated dtbs in /usr/share/dtb for now and set the dtb field in the deviceinfo for the n900 and my new qemu device. * Introduced linux-postmarketos-omap * Unified kernel progress * Created kernel bootable with qemu * Updated n900 deviceinfo for generic kernel * Changed qemu device to vexpress * Updated APK comments and added linux-postmarketos-dev package * Append dtb in mkinitfs * Fixed bootscript on n900 for the generic kernel * Don't detect double flavors with -dtb appending * Added graphics drivers for vexpress (qemu) * Added more drivers for qemu This adds virtio network support in qemu for the vexpress-a9 machine. The keyboard and mouse don't work yet. You can boot into weston if --no-fde is specified
2017-07-25 20:08:35 +00:00
license="MIT"
qemu-*: install mesa-dri-gallium (!1029) mesa-dri-swrast and mesa-dri-virtio are actually provided by the same package in Alpine now, so the selection in pmbootstrap does not have any use. Always install mesa-dri-gallium instead.
2020-03-06 10:44:08 +00:00
depends="postmarketos-base mesa-dri-gallium"
device/device-qemu-amd64: fix APKBUILD (!874)
2020-01-10 16:45:30 +00:00
makedepends="devicepkg-dev"
pmbootstrap init: kernel selection / remove linux-pmos-lts (#1363) * As discussed in IRC/matrix, we're removing `linux-postmarketos-lts` for now. The kernel isn't used right now, and we save lots of maintenance effort with not updating it every week or so. * new config option `"kernel"` with possible values: `"downstream", "mainline", "stable"` (downstream is always `linux-$devicename`) * ask for the kernel during `pmbootstrap init` if the device package has kernel subpackages and install it in `_install.py` * postmarketos-mkinitfs: display note instead of exit with error when the `deviceinfo_dtb` file is missing (because we expect it to be missing for downstream kernels) * device-sony-amami: * add kernel subpackages for downstream, mainline * set `deviceinfo_dtb` * device-qemu-amd64: add kernel subpackages for stable, lts, mainline * test cases and test data for new functions * test case that checks all aports for right usage of the feature: * don't mix specifying kernels in depends *and* subpackages * 1 kernel in depends is maximum * kernel subpackages must have a valid name * Test if devices packages reference at least one kernel * Remove `_build_device_depends_note()` which informs the user that `--ignore-depends` can be used with device packages to avoid building the kernel. The idea was to make the transition easier after a change we did months ago, and now the kernel doesn't always get built before building the device package so it's not relevant anymore. * pmb/chroot/other.py: * Add autoinstall=True to kernel_flavors_installed(). When the flag is set, the function makes sure that at least one kernel for the device is installed. * Remove kernel_flavor_autodetect() function, wherever it was used, it has been replaced with kernel_flavors_installed()[0]. * pmb.helpers.frontend.py: remove code to install at least one kernel, kernel_flavors_installed() takes care of that now.
2018-04-03 23:50:09 +00:00
subpackages="
$pkgname-weston
qemu-amd64: fix xfce4 background (!728) [ci:skip-build]: already built successfully in CI
2019-11-18 23:31:03 +00:00
$pkgname-xfce4
qemu-amd64: add option to use Alpine's linux-lts/linux-virt (!981)
2020-02-13 16:27:28 +00:00
$pkgname-kernel-virt:kernel_virt
$pkgname-kernel-lts:kernel_lts
pmbootstrap init: kernel selection / remove linux-pmos-lts (#1363) * As discussed in IRC/matrix, we're removing `linux-postmarketos-lts` for now. The kernel isn't used right now, and we save lots of maintenance effort with not updating it every week or so. * new config option `"kernel"` with possible values: `"downstream", "mainline", "stable"` (downstream is always `linux-$devicename`) * ask for the kernel during `pmbootstrap init` if the device package has kernel subpackages and install it in `_install.py` * postmarketos-mkinitfs: display note instead of exit with error when the `deviceinfo_dtb` file is missing (because we expect it to be missing for downstream kernels) * device-sony-amami: * add kernel subpackages for downstream, mainline * set `deviceinfo_dtb` * device-qemu-amd64: add kernel subpackages for stable, lts, mainline * test cases and test data for new functions * test case that checks all aports for right usage of the feature: * don't mix specifying kernels in depends *and* subpackages * 1 kernel in depends is maximum * kernel subpackages must have a valid name * Test if devices packages reference at least one kernel * Remove `_build_device_depends_note()` which informs the user that `--ignore-depends` can be used with device packages to avoid building the kernel. The idea was to make the transition easier after a change we did months ago, and now the kernel doesn't always get built before building the device package so it's not relevant anymore. * pmb/chroot/other.py: * Add autoinstall=True to kernel_flavors_installed(). When the flag is set, the function makes sure that at least one kernel for the device is installed. * Remove kernel_flavor_autodetect() function, wherever it was used, it has been replaced with kernel_flavors_installed()[0]. * pmb.helpers.frontend.py: remove code to install at least one kernel, kernel_flavors_installed() takes care of that now.
2018-04-03 23:50:09 +00:00
"
qemu-*: remove "USB" Internet hack, disable dhcpcd (!1029) QEMU has its own DHCP server, which provides the necessary routes and DNS server to access THE INTERNET. Trying to make QEMU provide something similar to our usual USB network (by starting our our DHCP server) will just confuse everything and break Internet access in most cases. Remove all our custom setup and let QEMU handle all the hard work.
2020-03-06 10:49:01 +00:00
source="deviceinfo weston.ini"
device-*: don't use noarch anymore Use the device's architecture instead of noarch. Because the device packages should never be built for other architectures, even if all depends can be built for other arches as well. This simplifies package building as part of the new build infrastructure effort. pmbootstrap has also been changed to output this by default in aportgen.
2018-11-07 06:45:58 +00:00
options="!check !archcheck"
Unified linux-postmarketos kernel for qemu and n900 (#228) The creates the linux-postmarketos package which for now supports the n900 (and probably the other maemo devices) and qemu with the vexpress-a9 machine simulation. I've put the generated dtbs in /usr/share/dtb for now and set the dtb field in the deviceinfo for the n900 and my new qemu device. * Introduced linux-postmarketos-omap * Unified kernel progress * Created kernel bootable with qemu * Updated n900 deviceinfo for generic kernel * Changed qemu device to vexpress * Updated APK comments and added linux-postmarketos-dev package * Append dtb in mkinitfs * Fixed bootscript on n900 for the generic kernel * Don't detect double flavors with -dtb appending * Added graphics drivers for vexpress (qemu) * Added more drivers for qemu This adds virtio network support in qemu for the vexpress-a9 machine. The keyboard and mouse don't work yet. You can boot into weston if --no-fde is specified
2017-07-25 20:08:35 +00:00
device/device-qemu-amd64: fix APKBUILD (!874)
2020-01-10 16:45:30 +00:00
build() {
devicepkg_build $startdir $pkgname
}
Unified linux-postmarketos kernel for qemu and n900 (#228) The creates the linux-postmarketos package which for now supports the n900 (and probably the other maemo devices) and qemu with the vexpress-a9 machine simulation. I've put the generated dtbs in /usr/share/dtb for now and set the dtb field in the deviceinfo for the n900 and my new qemu device. * Introduced linux-postmarketos-omap * Unified kernel progress * Created kernel bootable with qemu * Updated n900 deviceinfo for generic kernel * Changed qemu device to vexpress * Updated APK comments and added linux-postmarketos-dev package * Append dtb in mkinitfs * Fixed bootscript on n900 for the generic kernel * Don't detect double flavors with -dtb appending * Added graphics drivers for vexpress (qemu) * Added more drivers for qemu This adds virtio network support in qemu for the vexpress-a9 machine. The keyboard and mouse don't work yet. You can boot into weston if --no-fde is specified
2017-07-25 20:08:35 +00:00
package() {
device/device-qemu-amd64: fix APKBUILD (!874)
2020-01-10 16:45:30 +00:00
devicepkg_package $startdir $pkgname
Unified linux-postmarketos kernel for qemu and n900 (#228) The creates the linux-postmarketos package which for now supports the n900 (and probably the other maemo devices) and qemu with the vexpress-a9 machine simulation. I've put the generated dtbs in /usr/share/dtb for now and set the dtb field in the deviceinfo for the n900 and my new qemu device. * Introduced linux-postmarketos-omap * Unified kernel progress * Created kernel bootable with qemu * Updated n900 deviceinfo for generic kernel * Changed qemu device to vexpress * Updated APK comments and added linux-postmarketos-dev package * Append dtb in mkinitfs * Fixed bootscript on n900 for the generic kernel * Don't detect double flavors with -dtb appending * Added graphics drivers for vexpress (qemu) * Added more drivers for qemu This adds virtio network support in qemu for the vexpress-a9 machine. The keyboard and mouse don't work yet. You can boot into weston if --no-fde is specified
2017-07-25 20:08:35 +00:00
}
Fix #499: Don't generate weston.ini from the deviceinfo anymore (#739) @drebrez deserves much credit for this one for all the testing, bisecting and for fixing everything. Thank you very much! --- * devices which need a custom weston.ini ship it with a install_if subpackage, so it only gets installed when weston is installed. This sounds complicated, but is actually pretty clean in the APKBUILD. * postmarketos-ui-weston: has a weston.ini.default, which enables xwayland and uses fbdev as backend (because that's what most devices use!). It defaults to the weston.ini.default if there is no weston.ini (as installed by the device package). * changed spaces to tabs for consistency, general minor refactoring of device-APKBUILDs
2017-10-20 00:07:00 +00:00
weston() {
install_if="$pkgname weston"
install -Dm644 "$srcdir"/weston.ini \
"$subpkgdir"/etc/xdg/weston/weston.ini
}
qemu-amd64: fix xfce4 background (!728) [ci:skip-build]: already built successfully in CI
2019-11-18 23:31:03 +00:00
xfce4() {
install_if="$pkgname postmarketos-ui-xfce4"
install="$subpkgname.post-install"
mkdir "$subpkgdir"
}
qemu-amd64: add option to use Alpine's linux-lts/linux-virt (!981)
2020-02-13 16:27:28 +00:00
kernel_virt() {
qemu-*: drop linux-postmarketos-mainline/stable kernel option (!1029) We haven't been maintaining linux-postmarketos-mainline/stable very well. Let's recommend use of one of the Alpine kernels which are actively updated with new LTS updates (see #464). This simplifies upcoming refactoring of the QEMU device ports, which may (or may not) work with the more minimal kernel configurations in linux-postmarketos-mainline/stable.
2020-03-06 10:54:05 +00:00
pkgdesc="Alpine Virt kernel (minimal, no audio)"
qemu-amd64: add option to use Alpine's linux-lts/linux-virt (!981)
2020-02-13 16:27:28 +00:00
depends="linux-virt"
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
}
kernel_lts() {
pkgdesc="Alpine LTS kernel"
depends="linux-lts linux-firmware-none"
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
}
qemu-*: cleanup, use consistent hardware (!1029) pmbootstrap now configures consistent QEMU hardware for all architectures. This means that the device package for amd64/aarch64 is now almost identical, except for the architecture and the name of the serial port. pmbootstrap always uses virtio-gpu now (but not necessarily virgl), so there is only one consistent set of initfs modules we need to configure for both architectures. Also add the xfce4 package from amd64 to aarch64, exactly the same problem with the wallpaper exists there.
2020-03-06 13:01:14 +00:00
sha512sums="de21a746c2c7d2001238d0b266607b51007e319c7a645f2f3ca090285f628f7473b961741f480355b38df40de5892bbfba6012593b4b648b9724b1ba0b643a51 deviceinfo
qemu-*: remove "USB" Internet hack, disable dhcpcd (!1029) QEMU has its own DHCP server, which provides the necessary routes and DNS server to access THE INTERNET. Trying to make QEMU provide something similar to our usual USB network (by starting our our DHCP server) will just confuse everything and break Internet access in most cases. Remove all our custom setup and let QEMU handle all the hard work.
2020-03-06 10:49:01 +00:00
47b27c7572b8737988488f7eb23b9e68f9a944e22baafe1c78355d2514a2554cf41d99b29fca12238eb13a6f5d53f00ca89b94e534e8461ebab72256dcf0f142 weston.ini"
Reference in a new issue Copy permalink