7f65cb1a6b
0001-remove-hardcoded-path.patch 0002-Do-not-build-qt-tests.patch refreshed for 1.0.4 Changelog: =========== Features: * bundle: Add AS_BUNDLE_KIND_SYSUPDATE * desktop-style-ids: Add dark support for Plasma * desktop-style-ids: add pantheon:dark * qt: Expose branding color * sysinfo: Add memory size detection support for Illumos and Solaris * sysinfo: Add memory size detection support for GNU/Hurd * validator: Don't fail validation if a snapshot release is missing a time Specification: * docs: Note that support for some legacy path was dropped in 1.0 * docs: Update fd.o spec URLs * docs: Better explain desktop applications * Update ESRA website URL Bugfixes: * validator: Make sure we read an initialised variable * qt: Specify utc as the dates' timezone * tests: Ignore some tests on Windows * sysinfo: make uname() usage POSIX compliant * Only emit legacy compat tag developer_name for catalog data * compose: Allow file discovery even in symlinked directories * Avoid a race condition when loading GResource data * validator: Mention length limit in summary length warning message * utils: Explicitly set permissions on installed metadata files * as-vercmp: Fix gtkdoc to not start with '>' Miscellaneous: * desktop-style-ids: Remove Endless * ci: Fix FreeBSD build (update 'py-gi-docgen') * ci: Update to Ubuntu 24.04 for Debian Testing builds * utils: Assume 64px as size when installing an icon tarball of unknown size (From OE-Core rev: 9655af038a0bc7d6775858e6c32d302eec5b3b9b) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.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
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
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.