5c6b76aad3
v10.4.0
* What's Changed
- Issue 854: sample improvements by @bbayles in #855
- Issue 858: Use chain and starmap in run_length.decode by @bbayles
in #861
- Issue 859: Update totient recipe by @bbayles in #860
- Distinct permutations of incomparable items by @JamesParrott in #834
- Clarify seekable.relative_seek behavior by @bbayles in #863
- Issue 864: Improve _sample_unweighted by @bbayles in #865
- Use log1p for _sample_unweighted by @bbayles in #868
- Issue 862: change relative_seek() behaviour by @dkrikun in #866
- Issue 876: is_sorted clarifications by @bbayles in #877
- Issue 870: counts parameter for sample by @bbayles in #875
- Issue 869: Add a steps argument to circular_shifts by @bbayles in #874
- Issue 871: Add a fast path for sliding_window by @bbayles in #873
- type annotation of windowed_complete corrected by @m472 in #881
- [Docs] Fix strictly_n missing the n parameter by @fakuivan in #886
- Standardize type hints for isinstance's second argument by @jbosboom
in #887
- Issue 883: change type hint by @akisatoon1 in #884
- Add type overloads for zip_broadcast by @Pandede in #888
- Issue 889: Optimize triplewise by @bbayles in #891
- Add option strict to sort_together by @Pandede in #892
- Updates for version 10.4.0 by @bbayles in #893
(From OE-Core rev: 484401a7608c1467d17f82d8056234bb39e9b0b5)
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>
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.