Trevor Gamblin edfab1a3ce python3-meson-python: upgrade 0.16.0 -> 0.17.1
Changelog (https://mesonbuild.com/meson-python/changelog.html):

0.17.1

    - Update tests to work with newly released pyproject-metadata 0.9.0.
      Fix tests to work when not executed in a git work tree.

Daniele Nicolodi — 23-10-2024.

0.17.0

    - Refuse to build wheels targeting the limited API and free-threaded
      CPython: the free-threaded CPython build does not support the
      limited API yet.
    - Always use UTF-8 encoding for writing Meson native and cross
      files. Always use UTF-8 encoding for reading read Meson
      introspection data and pyproject.toml.
    - Do not include uncommitted changes when creating source
      distributions. Previously, uncommitted changes to files under
      version control were included, but not untracked files. There was
      no strong use case for this behavior and it was too surprising to
      keep it.
    - Make source distribution reproducible: use the modification time
      of pyproject.toml for the generated files in the source
      distribution archives.
    - Disable the abi3 wheel tag for PyPy when building wheels targeting
      the limited API: PyPy supports the limited API but not the stable
      ABI.
    - Raise ImportError when the package rebuild fails when importing an
      editable install.
    - Fix the wheel platform tag for GraalPy.
    - Add .gitignore and .hgignore files to build directory if it is
      empty.
    - Allow install_subdir() of missing directories.

Christian Clauss, Daniele Nicolodi, Jonathan J. Helmus, Leo Singer, Loïc
Estève, Michael Simacek, Ralf Gommers, Simon McVittie — 19-10-2024.

(From OE-Core rev: 27a818f8e7d7abafea48cf84baaaf510916f6c86)

Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-11-22 16:58:40 +00:00
2024-02-19 11:34:33 +00:00
2021-07-19 18:07:21 +01:00
2023-10-19 11:31:13 +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

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

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 251 MiB