Wang Mingyu bf0b19cf8d mc: upgrade 4.8.29 -> 4.8.30
0001-mc-replace-perl-w-with-use-warnings.patch
removed since it's included in 4.8.30

Changelog:
==========
- Core
--------
    * Support PCRE2 as search engine (via ----with-search-engine=pcre2) (#4450)
    * Implement panelization buffers for both file panels (#4370)

- VFS
-------
    * tar: support extended headers (including long file names and sparse files) (#1952, #2201)
    * extfs helpers: replace "perl -w" with "use warnings" (MidnightCommander/mc#174)
    * extfs/patchfs: be more specific in error message (#4485)

- Editor
---------
    * Add syntax highlighting:
        - Jenkinsfiles (#4469)
        - B language (#4470)
    * Improve syntax highlighting:
        - ECMAScript (MidnightCommander/mc#172)
        - ECMAScript in TypeScript (MidnightCommander/mc#172)
        - use diff syntax highlighting for git commit messages (COMMIT_EDITMSG) (MidnightCommander/mc#85)

- Misc
--------
    * Code cleanup (#4426, #4438)
    * Filehighlight:
        - recognize vsix files as zip files (MidnightCommander/mc#171)
    * Skin updates:
        - julia256 (#4441, #4445)

- Fixes
----------
    * Usage of 'sed' in build system/makefiles is not portable (#4459, #4466)
    * Unportable '$<' in Makefiles (#4460)
    * FTBFS if ncurses used without --with-ncurses-includes= configure parameter (#4462)
    * Ncurses library is duplicated in MCLIBS (#4463, #4465)
    * FTBFS without ext2fs attributes support (#4464)
    * Wrong sort order after swapping panels (#4432)
    * Incorrect time delimiter in the copy/move progress window (#4437)
    * Incorrect redraw of overlapped file panels (#4408)
    * Subshell/Command line prompt is empty/missing (#3121)
    * Find file: relative ignore directory is applied to the start search directory (#4235)
    * Diff viewer: options are not applied on second run (#4486)
    * mc.ext.ini: 'Edit' command from 'Default' section is ignored (#4434)
    * mc.ext.ini: .md files are not recognized as Markdown ones by extension (#4444)
    * mcedit: off-by-one error in paragraph formatting (#4446)
    * ftp: incomplete file listing: block and character devices, pipes, sockets are missed (#4472)
    * Various typos in the source code (MidnightCommander/mc#177, MidnightCommander/mc#178)

(From OE-Core rev: 9ba1f7042de6e430c687970657173740eec9ea7b)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-09-02 18:23:05 +01:00
2023-09-02 18:23:05 +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

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