ca44c2d0dc
Upgrade libxpm 3.5.13 to 3.5.15 License-update: additional copyright holders f0857c0 man pages: Correct Copyright/License notices The above commit is introduced while upgrading the libxpm 3.5.15. which is mentioned in below changelog. Due to this commit LIC_FILES_CHKSUM is changed. Disable reading compressed files as that requires compress/uncompress executables. Following the approach in oe-core/master: 7de4084634 libxpm: upgrade 3.5.14 -> 3.5.15 Changelog: ------------- ------------- ddd8339 libXpm 3.5.15 8178eb0 Use gzip -d instead of gunzip c5ab17b Prevent a double free in the error code path 515294b Fix CVE-2022-4883: compression commands depend on $PATH f80fa6a Fix CVE-2022-44617: Runaway loop with width of 0 and enormous height f7fbbb9 test: add test cases for CVE-2022-44617 (zero-width w/enormous height) a3a7c6d Fix CVE-2022-46285: Infinite loop on unclosed comments f7a167a test: add test case for CVE-2022-46285 (unclosed comments) 0ff2c6a cxpm: getc/ungetc wrappers should not adjust position when c == EOF 501494c test: Add unit tests using glib framework 4841039 configure: add --disable-open-zfile instead of requiring -DNO_ZPIPE aef0c8d man pages: Apply standard man page style/formatting 5d55a0b man pages: Replace "See Also" entries with more useful ones 392cb8f man pages: Fix typos and other minor editing 08bc174 libXpm 3.5.14 f0857c0 man pages: Correct Copyright/License notices deb81a9 man pages: Fix typos 2d5fa4c man pages: Add missing word 'function' where needed 2b7357e man pages: Make function synopses more consistent with other pages fb8590c man pages: Fix shadow man pages bfaebfd man pages: Make file names consistent with their displayed names 7a138a5 gitlab CI: add a basic build test 3433f43 man: strip trailing whitespace 9612454 Fix spelling/wording issues fa16fbd Build xz tarballs instead of bzip2 83e5427 update man pages e48e649 add man pages based on doc/xpm.PS (From OE-Core rev: a549319e5fdae685f93122627226f9b102307bc3) Signed-off-by: Yogita Urade <yogita.urade@windriver.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
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.