GO package dependencies are a tricky beast. They are source
dependencies and if you have two packages which share a dependency
they could very well require different versions of the dependency. So
supplying the dependencies via bitbake recipes is not an easy
proposition. As such we are better off populating the build source
with the dependencies using SRC_URIs and not traditional DEPENDS.

That being said, the consul source repository actually includes copies
of the dependencies (and the dependency's dependencies) so having
these DEPENDS is actually useless and we can simply drop them.

Signed-off-by: Mark Asselstine <[email protected]>
---
 recipes-connectivity/consul/consul_git.bb | 34 -------------------------------
 1 file changed, 34 deletions(-)

diff --git a/recipes-connectivity/consul/consul_git.bb 
b/recipes-connectivity/consul/consul_git.bb
index bcfb5aa..5f86597 100644
--- a/recipes-connectivity/consul/consul_git.bb
+++ b/recipes-connectivity/consul/consul_git.bb
@@ -3,40 +3,6 @@ HOMEPAGE = "https://www.consul.io/";
 LICENSE = "MPL-2.0"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=b278a92d2c1509760384428817710378"
 
-DEPENDS += "circbuf \
-    consul-migrate \
-    go-checkpoint \
-    go-msgpack \
-    go-metrics \
-    go-bindata \
-    go-sys \
-    go-syslog \
-    dockerclient \
-    logutils \
-    memberlist \
-    raft \
-    raft-boltdb \
-    scada-client \
-    serf-go \
-    yamux \
-    muxado \
-    dns \
-    cli \
-    mapstructure \
-    copystructure \
-    reflectwalk \
-    columnize \
-    go-radix \
-    golang-lru \
-    hashicorp-hil \
-    hashicorp-hcl \
-    hashicorp-go-cleanhttp \
-    hashicorp-go-memdb \
-    hashicorp-go-reap \
-    hashicorp-go-uuid \
-    net-rpc-msgpackrpc \
-    "
-
 PKG_NAME = "github.com/hashicorp/consul"
 SRC_URI = "git://${PKG_NAME}.git \
            file://consul.service \
-- 
2.7.4

-- 
_______________________________________________
meta-virtualization mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-virtualization

Reply via email to