linux/poky.git/meta/recipes-core/readline, branch yocto-2.5.2

readline: Add HOMEPAGE info into recipe file.

2017-09-05T14:01:01+00:00

(From OE-Core rev: 516e0dda595c3c40bda4f4d3f4fd86225ace55c9) Signed-off-by: Fan Xin Signed-off-by: Richard Purdie

readline: Remove unused patch

2017-03-16T22:11:32+00:00

config-dirent-symbols.patch was removed from SRC_URI as "already applied in upstream" in 983a4986947. (From OE-Core rev: 43e764a54458c9c6665bb7734b1fc7e7956bffdc) Signed-off-by: Jussi Kukkonen Signed-off-by: Richard Purdie

recipes: Move out stale GPLv2 versions to a seperate layer

2017-03-07T20:05:31+00:00

These are recipes where the upstream has moved to GPLv3 and these old versions are the last ones under the GPLv2 license. There are several reasons for making this move. There is a different quality of service with these recipes in that they don't get security fixes and upstream no longer care about them, in fact they're actively hostile against people using old versions. The recipes tend to need a different kind of maintenance to work with changes in the wider ecosystem and there needs to be isolation between changes made in the v3 versions and those in the v2 versions. There are probably better ways to handle a "non-GPLv3" system but right now having these in OE-Core makes them look like a first class citizen when I believe they have potential for a variety of undesireable issues. Moving them into a separate layer makes their different needs clearer, it also makes it clear how many of these there are. Some are probably not needed (e.g. mc), I also wonder whether some are useful (e.g. gmp) since most things that use them are GPLv3 only already. Someone could now more clearly see how to streamline the list of recipes here. I'm proposing we mmove to this separate layer for 2.3 with its future maintinership and testing to be determined in 2.4 and beyond. (From OE-Core rev: 19b7e950346fb1dde6505c45236eba6cd9b33b4b) Signed-off-by: Richard Purdie

readline: Update to version 7.0

2016-11-23T11:10:11+00:00

Remove readline 6.3 patches and config-dirent-symbols.patch already apply on upstream. (From OE-Core rev: 983a4986947b63e9b6042fc8c083cde3bc1c30ad) Signed-off-by: Fabio Berton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

readline: don't install readline C examples

2016-08-01T10:47:14+00:00

They are unlikely to be of any use in the target file system. (From OE-Core rev: 5889583b3961bf09ae32418777b06db3a02816b1) Signed-off-by: André Draszik Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

readline: move inputrc into readline

2016-01-07T13:40:19+00:00

inputrc is the global configuration file for the readline library. (From OE-Core rev: 619d15b9a2c53eb8496c807f0f229f5cb192e9d7) Signed-off-by: Joseph A. Lutz Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

readline: apply missing upstream patches

2015-12-01T21:32:10+00:00

Some readline-6.3 upstream patches was missing. Also ensure that the upstream patches are applied in the same way as in readline-5.2. Remove 'readline-dispatch-multikey.patch' and 'readline-cve-2014-2524.patch' since they are already included in upstream patches 'readline63-002' and 'readline63-003'. [YOCTO #8451] (From OE-Core rev: 7b1fde3f65b674f5973800731c0c284f7d415248) Signed-off-by: Petter Mabäcker Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

readline: prepare for readline6.3 upstream patches

2015-12-01T21:32:10+00:00

Upstream patches are always preferred to be applied first (before integration patches). In order to apply readline-6.3 specific upstream patches in a preferred order we need to apply the integration-patches at the end in the 6.3 specific recipe (this is already the case for readline-5.2). Also take the oppertunity to move 'norpath.patch' to readline-6.3 dir since this patch is not shared between the 5.2 and 6.3 recipe. [YOCTO #8451] (From OE-Core rev: d454d1c06247b658c6b7d12de610eb6ac72cd7d4) Signed-off-by: Petter Mabäcker Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

readline: rename patch to contain CVE reference

2015-11-16T11:39:33+00:00

To help automated scanning of CVEs, put the CVE ID in the filename. (From OE-Core rev: 211bce4f23230c7898cccdb73b582420f830f977) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

readline: actually apply readline63-003 (aka CVE-2014-2524)

2015-10-06T23:11:21+00:00

This file wasn't named as a patch, nor told to apply explicity, so it was just unpacked to the work directory and not applied. Rename the file so the patch is applied correctly. (thanks to Petter Mabäcker for spotting this) (From OE-Core rev: 02be728762c77962f9c3034cd7995ad51afaee95) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie