2c6d12ec3a
Changelog: =========== - implement a fix for CVE-2022-4170 (reported and analyzed by David Leadbeater). While present in version 9.30, it should not be exploitable. It is exploitable in versions 9.25 and 9.26, at least, and allows anybody controlling output to the terminal to execute arbitrary code in the urxvt process. - the background extension no longer requires off focus fading support to be compiled in. - the confirm-paste extension now offers a choice betwene pasting the original or a sanitized version, and also frees up memory used to store the paste text immediately. - fix compiling without frills. - fix rewrapMode: never. - fix regression that caused urxvt to no longer emit responses to OSC color queries other than OSC 4 ones. - fix regression that caused urxvt to no longer process OSC 705. - restore CENTURY to be 1900 to "improve" year parsing in urclock (or at least go back to the old interpretation) (based on an analysis by Tommy Pettersson). - exec_async (used e.g. by the matcher extension to spawn processes) now sets the URXVT_EXT_WINDOWID variable to the window id of the terminal. - implement -fps option/refreshRate resource to change the default 60 Hz maximum refresh limiter. I always wanted an fps option, but had to wait for a user requesting it. - new clickthrough extension. - perl now also requires Xext. - X region and shape extension functionality has been exposed to perl extensions. - RENDER extension no longer depends on ENABLE_XIM_ONTHESPOT. (From OE-Core rev: 9caf2cbd7dd82e72d0a04052fc93435f62e249ce) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.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.