188a59b06a
Security update CVE fixed in this release: CVE-2022-2319/ZDI-CAN-16062: X.Org Server ProcXkbSetGeometry Out-Of-Bounds Access CVE-2022-2320/ZDI-CAN-16070: X.Org Server ProcXkbSetDeviceInfo Out-Of-Bounds Access Changes: present: Check for NULL to prevent crash rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined) X11Application: Ensure TIS operations are done on the main thread os/connection: Improve abstraction for launchd secure sockets xquartz: Create a separate category for organizing user preferences xquartz pbproxy: Adopt NSUserDefaults+XQuartzDefaults for preferences xquartz: Fold spaces related preferences into NSUserDefaults+XQuartzDefaults XQuartz: Ensure scroll events are delivered to a single window (not both X11 and AppKit) meson: Bump requirement to meson-0.50.0 xquartz: Update Sparkle configuration to use SUPublicEDKey xquartz: Update copyright for 2022 meson: Provide options to set CFBundleVersion and CFBundleVersionString in XQuartz Revert "meson: Bump requirement to meson-0.50.0" xquartz: Update autotools-based builds of XQuartz to account for recent changes print_edid: Fix a format string error xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK tests: Fix build failure from missing micmap.c meson: Support building Xnest and Xorg on darwin XQuartz: Build the bundle trampoline when using meson XQuartz: Add TCC reason keys to Info.plist xquartz: Use correct defines when building to support Sparkle updates xquartz: Fix a possible crash when editing the Application menu due to mutaing immutable arrays XQuartz: Improve type safety for X11Controller's application menu editor xquartz: Add missing files to distribution tarball render: Fix build with gcc 12 xkb: switch to array index loops to moving pointers xkb: swap XkbSetDeviceInfo and XkbSetDeviceInfoCheck xkb: add request length validation for XkbSetGeometry Revert "os: Try to discover the current seat with the XDG_SEAT var first" dix: Correctly save replayed event into GrabInfoRec dix: Don't send touch end to clients that do async grab without touches xfree86: Fix event data alignment in inputtest driver xkb: fix XkbSetMap when changing a keysym without changing a keytype (From OE-Core rev: 75503a13cb2a2266f311477a605389bbac7676e2) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit d683f2a1fbe65b52d82f55a2e38aa75fc105a338) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.