Markus Volk 11651df0f6 epiphany: update 45.3 -> 46.0
46.0 - March 15, 2024
=====================

 * Improve keyboard navigation of address bar dropdown (#1726, Markus Göllnitz)
 * Add "Send Link by Email..." to context menu for links (#2037, Leon Marz)
 * Use selected text when middle clicking on New Tab button (#2159)

46.rc - February 29, 2024
===========================

 * Close security popover after selection (#2215)
 * Focus location entry on search hotkey (#2278)
 * Close page menu popover on print, search and fullscreen actions (#2283)
 * Forward key events directly to web view (#1915) (#2173)
 * Updated translations

46.beta - February 10, 2024
===========================

 * Fix a crash (#2021)
 * Allow closing pinned tabs (#2264)
 * Adjust labels to improve HIG compliance (!1431, Bart Gravendeel)
 * Support PKCS #11 smart card authentication (!1433)
 * Updated translations

46.alpha - January 5, 2024
==========================

 * Use web app manifest to get better app name and icon (#931)
 * Prevent websites from using certain Epiphany internal APIs (#1664)
 * Fix poor Firefox Sync error message when gnome-keyring is not installed (#1755)
 * Reduce adblock filter update interval on metered connections (#2152)
 * Rename Firefox Account to Mozilla Account (#2231)
 * Hide various context menu items when text is selected (#2258)
 * Remove Google Safe Browsing support due to terms of service changes (!335)
 * Hide developer context menu actions by default (!1392, Vitaly Dyachkov)
 * Update to highlight.js 11.9.0 (!1394)
 * Use AdwSpinRow in preferences dialog (Pig, !1411)
 * Many improvements to appstream metainfo (Sabri Ünal, !1398, !1399, !1414, !1422, !1425)
 * Updated translations

(From OE-Core rev: c7384afa31f76e9e547a1a0af819707b90699e5b)

Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-04-04 14:05:03 +01:00
2024-04-04 14:05:03 +01: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 249 MiB