capabilities: tie recipe to git revision instead of dynamicly generated tarball

Since Github's auto-generated tarballs aren't garanteed to be identical
over time it's better to tie the recipe to a git revision.

contributes to #552

Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
This commit is contained in:
Dmitry Rozhkov 2017-09-20 08:56:17 +03:00
parent dfeb9aa136
commit a211d16b51
1 changed files with 3 additions and 4 deletions

View File

@ -5,11 +5,10 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=62135a7570582b9018c89013d4815380"
DEPENDS = "message-generation roslaunch rospy std-msgs std-srvs" DEPENDS = "message-generation roslaunch rospy std-msgs std-srvs"
SRC_URI = "https://github.com/osrf/${ROS_SPN}/archive/${PV}.tar.gz;downloadfilename=${ROS_SP}.tar.gz" SRC_URI = "git://github.com/osrf/${PN}.git;branch=master;protocol=git"
SRC_URI[md5sum] = "0071ef2532612c7cc60c2b5a423d38d6" SRCREV = "c6c71a9ac17e310787242f5b75bd1e4d86349844"
SRC_URI[sha256sum] = "e55564dd82373139a4758d9d9e85d697bed6a0487c018774913e0f7069ce4024"
S = "${WORKDIR}/${ROS_SP}" S = "${WORKDIR}/git"
inherit catkin inherit catkin