Tim Orling f1bb4f7eb5 python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
* Require Python 3.8 or later.

34fd736 (HEAD, tag: v6.8.0) Finalize
97084d8 Remove reliance on typing-extensions, only required for Python 3.7 compatibility.
b74d2b2 Merge pull request #460 from Gryfenfer97/main
ec7bca0 Disable tests on pypy due to #463
ee4f84a Remove superfluous includes
f862e3f Merge branch '2023-handoff' of https://github.com/jaraco/skeleton
23ed6b1 Merge branch 'collapse' into 2023-handoff
c29955f Collapse skeleton history. Workaround for jaraco/skeleton#87.
cca49a4 Prefer 3.x for Python version (latest stable).
74ba8ac Leverage pytest-enabler 2.2 for the default config.
8e83c3f Expand 'finalize' to commit and tag the change.
f5a5617 Merge https://github.com/jaraco/skeleton
3b7d8a9 Require Python 3.8 or later.
07a87ea Remove tox boilerplate, no longer necessary with later versions of tox.
cd145f4 Replace workaround for actions/setup-python#508 with 'allow-prereleases'
5ca761c Merge https://github.com/jaraco/skeleton
45c03bd add typing for simple functions
74b0d39 Adopt towncrier for managing changelog. Fixes jaraco/skeleton#83.
2963377 Merge https://github.com/jaraco/skeleton
241541c Remove inclusion of python version for docs
e7cd730 Add badge for Ruff.
6f75480 Update RTD boilerplate to new issue. Ref readthedocs/readthedocs.org#10401.

(From OE-Core rev: bc820ff2f8d255783bedc28e468ee2e1d7de873b)

Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-07-14 17:31:06 +01:00
2021-07-19 18:07:21 +01:00

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/):

BitBake (files in bitbake/):

Documentation (files in documentation/):

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

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.

CII Best Practices

Description
No description provided
Readme 249 MiB