Wang Mingyu c0b4de5ad5 bash-completion: upgrade 2.14.0 -> 2.15.0
Changelog:
===========
* _comp_abspath:** handle ".."
* _comp_compgen_filedir,_comp_compgen_filedir_xspec:** don’t suggest . nor .. nor */. nor */.. unless the user input is .. or */..
* associate unzip and friends with *.vsix
* curl:** Complete "%", "-" for --trace[-ascii]
* curl:** Complete files for --json, --write-out
* curl:** Complete stdin "-" in file locations
* fprintd-*:** new completions
* iftop:** -G, -s, -L, and -o arg (non-)completions
* ip:** complete ip ntable show
* java:** enable .java filename completion for java command
* kata-runtime:** add 3rd party fallback completion loader
* nerdctl:** add 3rd party fallback completion loader
* ngrok:** add 3rd party fallback completion loader
* openssl:** Stop having subcommands hardcoded
* python,pyvenv:** versioned 3.13 executable support
* set:** more featureful completion
* slabtop:** new completion
* sops:** add 3rd party fallback completion loader
* tar:** use long option compression options
* todoist:** add 3rd party fallback completion loader
* uv:** add 3rd party fallback completion loader
* uvx:** add 3rd party fallback completion loader
* wine:** complete with '*.bat' and '*.cmd'
* xv:** associate with *.webp and *.pnm
* xxd:** add -n, -o, and -R arg (non-)completions
* _comp_compgen:** use 'compgen -V array_name' in 'bash >= 5.3'
* _comp_expand_glob:** set LC_COLLATE for the sorting order
* _comp_expand_glob:** work around GLOBSORT in Bash 5.3
* compatdir:** use _comp_expand_glob for the correct order
* curl:** Complete all and category for --help
* dpkg:** Add missing short option -R
* rsync,ssh:** do not overescape spaces in remote filenames
* source files using absolute paths for absolute BASH_SOURCE
* tar:** Complete added files with long opts
* update-alternatives:** fix the "--help" parsing

(From OE-Core rev: 35ab69c7b824cb51b5bf869beb16eb118331c176)

Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-12-12 12:52:39 +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