Yi Zhao abd46facfa tcl8: upgrade 8.6.16 -> 8.6.17
ChangeLog:
  2024-12-16 (bug) [63449c] [namespace children] doesn't match non-glob
             patterns below the global namespace
  2025-01-06 (bug) [fc3509] Better error-message than "interpreter uses
             an incompatible stubs mechanism"
  2025-01-19 tzdata updated to Olson's tzdata2025a
  2025-01-28 (bug) [4f0b57] Win: [exec] now works on App Execution
             Aliases.
  2025-01-28 (bug) [4e2c8b] Win: [auto_execok] handles larger set of
             shell commands.
  2025-03-06 (bug) [ba68d1] errorline from [interp eval], interp-26.9
  2025-03-23 tzdata updated to Olson's tzdata2025b
  2025-04-11 (bug) [fd8341] Tcl_InitStubs compatibility for 9.1, better
             error-handling
  2025-05-05 (bug) [42d14c] Fix scan with long mantissa. Ex.: scan
             "1.[string repeat 1 191]e-321" %g
  2025-06-18 (bug) [4f338b] add missing Tcl_CloseEx docs
  2025-06-24 (bug) [ecf35c] Correct nested handling of return option
             -options
  2025-06-25 (bug) [ecafd8] Euro/Tail-sign missing from cp864 encoding
  2025-07-03 (bug) [6b0f77] gcc 14 breaks configure test for bigendian
             leading to broken floating point
  2025-07-16 (bug) [c9f052] prevent overflow crash in Tcl_SplitList().
  2025-07-21 (bug) [61c01e] Flawed ref counts in filesystem
             implementation for Windows led to use-after-free
  2025-08-12 (new) dde => 1.4.5
  2025-08-12 (bug) [992f94] avoid misaligned pointers in macOS file
             attribute functions

Set LC_ALL and LANG to en_US.UTF-8 when running ptest since the test
cases now include more encodings than just ASCII[1].
Also, add rdepends on locale-base-en-us and tzdata for ptest package,
as they are required for running ptest.

[1] aca3422d8b

(From OE-Core rev: 77cfa81c065cbdd31db1245379d7b9ec1dc224ae)

Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2025-10-09 10:58:07 +01:00
2025-10-09 10:58:07 +01:00
2024-02-19 11:34:33 +00: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

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