db: don't provide virtual/db

As there are no alternative providers for virtual/db remove the PROVIDES and
recipes can just depend on db.

Signed-off-by: Ross Burton <ross.burton@intel.com>

diff --git a/meta/recipes-support/db/db_5.3.28.bb b/meta/recipes-support/db/db_5.3.28.bb
index fb4befbaf738d93fa0e90ab46554f51d9238babe..fe71967715e7cb7d9a722188c233aca4485d74f8 100644 (file)
--- a/meta/recipes-support/db/db_5.3.28.bb
+++ b/meta/recipes-support/db/db_5.3.28.bb
@@ -12,7 +12,6 @@ SECTION = "libs"
 SUMMARY = "Berkeley Database v5"
 HOMEPAGE = "http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/overview/index.html"
 LICENSE = "Sleepycat"
-VIRTUAL_NAME ?= "virtual/db"
 RCONFLICTS_${PN} = "db3"
 
 PR = "r1"
@@ -37,15 +36,6 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=ed1158e31437f4f87cdd4ab2b8613955"
 
 inherit autotools
 
-# Put virtual/db in any appropriate provider of a
-# relational database, use it as a dependency in
-# place of a specific db and use:
-#
-# PREFERRED_PROVIDER_virtual/db
-#
-# to select the correct db in the build (distro) .conf
-PROVIDES += "${VIRTUAL_NAME}"
-
 # The executables go in a separate package - typically there
 # is no need to install these unless doing real database
 # management on the system.