summaryrefslogtreecommitdiff
path: root/meta/recipes-connectivity
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2011-07-05 14:33:02 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-07-07 10:49:48 +0100
commit84f3ae92ab4345cc99b47e021ff960857f803d45 (patch)
tree3a266fa69f709137d622c3eaef8f3d1503387430 /meta/recipes-connectivity
parentb2713b0bd8c8f01a6c1bbd94e8ebc5d780e32220 (diff)
downloadopenembedded-core-84f3ae92ab4345cc99b47e021ff960857f803d45.tar.gz
openembedded-core-84f3ae92ab4345cc99b47e021ff960857f803d45.tar.bz2
openembedded-core-84f3ae92ab4345cc99b47e021ff960857f803d45.zip
openssh/dropbear: No need for each to PROVIDE ssh/sshd
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-connectivity')
-rw-r--r--meta/recipes-connectivity/openssh/openssh_5.8p2.bb1
1 files changed, 0 insertions, 1 deletions
diff --git a/meta/recipes-connectivity/openssh/openssh_5.8p2.bb b/meta/recipes-connectivity/openssh/openssh_5.8p2.bb
index ec33b29681..e23069cb77 100644
--- a/meta/recipes-connectivity/openssh/openssh_5.8p2.bb
+++ b/meta/recipes-connectivity/openssh/openssh_5.8p2.bb
@@ -12,7 +12,6 @@ PR = "r0"
DEPENDS = "zlib openssl"
DEPENDS += "${@base_contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)}"
-PROVIDES = "ssh sshd"
RPROVIDES = "ssh sshd"
CONFLICTS_${PN} = "dropbear"