linux/poky.git/meta/recipes-core/dropbear/dropbear.inc, branch 1.2_M4.rc1

dropbear: Upgrade from 0.52 to 0.53.1

2011-10-04T12:46:20+00:00

(From OE-Core rev: f1710d09e447b0f71a55b4ef24673c6388a045ad) Signed-off-by: Mei Lei Signed-off-by: Richard Purdie

dropbear: Change the path to find configuration file and add a configuration file for dropbear

2011-08-31T18:59:59+00:00

dropbear will check "/etc/pam.d/sshd" which comes from package "openssh" \ When enabling pam supporting. But if we only install dropbear \ package without package "openssh", then "dropbear" will not \ find a configuration file. The changes are as follow for fixing this bug: - Change the path to find configuration file (/etc/pam.d/sshd --> /etc/pam.d/dropbear) - Add a configuration file "/etc/pam.d/dropbear" (From OE-Core rev: 48dcb8fc7b669b27160dde33079f40551853702b) Signed-off-by: Xiaofeng Yan Signed-off-by: Richard Purdie

dropbear: Support pam

2011-07-27T11:02:43+00:00

I make a patch and some changes in dropbear.inc for supporting pam. - Enable pam in configure - Modify file option.h to open pam supporting (From OE-Core rev: e8f19e8616fb1b0c2d977fb63eaa64f504fb774b) Signed-off-by: Xiaofeng Yan Signed-off-by: Richard Purdie

dropbear: don't override DISTRO_TYPE if it is already set

2011-07-27T11:02:40+00:00

The long term solution is to remove the IMAGE_FEATURE check since images are not allowed to influence recipe compile options. (From OE-Core rev: 1c24f36e982e680871bf7a05ac6e820314e19c7c) Signed-off-by: Koen Kooi Signed-off-by: Richard Purdie

openssh/dropbear: No need for each to PROVIDE ssh/sshd

2011-07-07T09:57:51+00:00

Nothing in the system actually uses the PROVIDES field for these recipes, its usually the runtime packages that are used. We can therefore remove the PROVIDES and hence quieten the associated warnings from bitbake. If these recipes do really need the PROVIDES, they would be better as virtuals and adding that to MULTI_PROVIDER_WHITELIST. (From OE-Core rev: 84f3ae92ab4345cc99b47e021ff960857f803d45) Signed-off-by: Richard Purdie

dropbear: Don't patch in configure

2011-06-23T11:07:32+00:00

We need to avoid applying a patch in configure, because a rebuild could trigger this, without triggering do_patch. (From OE-Core rev: 16fbdaa24fd4add37c1e873505f55bcef5695a94) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

Remove distro-specific metadata for distros not in oe-core

2011-05-05T11:26:30+00:00

(From OE-Core rev: ea2cd4b8e9bc013a007fe2a1a605ecb59db5a896) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

logging: update existing oe* logging users to the bb* interface

2011-05-03T23:54:37+00:00

The new bash logging class provides bbnote, bbwarn, bbfatal, and bbdebug replacements (as well as bbplain and bberror) for the oe* equivalents. Use the new bb* API in preparation to delete the oe* logging API. This patch was automatically generated by a sed script. The result has been visually inspected and used to build core-image-sato for qemux86. (From OE-Core rev: a1f09fce5caba389d0484b169f0cde85d64514fa) Signed-off-by: Darren Hart Signed-off-by: Richard Purdie

recipes: pre/post actions

2011-02-12T00:31:43+00:00

A number of the recipes did not properly label their pre and post actions, causing the actions to occur in all split packages. This was corrected by defaulting to _${PN} in most cases. Signed-off-by: Mark Hatle

recipes-core: Cleanup package descriptions and summaries

2010-10-11T21:15:10+00:00

[BUGID #281] Evaluate and update each package in recipes-core to ensure they have a consistent summary and description. Signed-off-by: Mark Hatle