image-transport-plugins: tie recipes to git revision instead of dynamicly generated tarballs
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:
parent
22e8967a9c
commit
3cb48e5df3
|
@ -1,8 +1,7 @@
|
|||
SRC_URI = "https://github.com/ros-perception/${ROS_SPN}/archive/${PV}.tar.gz;downloadfilename=${ROS_SP}.tar.gz"
|
||||
SRC_URI[md5sum] = "f5b776df0be6a325f8615c8034b1c278"
|
||||
SRC_URI[sha256sum] = "a3dcd3af617bcafba5b8dab5fbd89183fbaf31798ee4e4e63a91059fa110168c"
|
||||
SRC_URI = "git://github.com/ros-perception/${ROS_SPN}.git;branch=indigo-devel;protocol=git"
|
||||
SRCREV = "812093c8342112bca3ac62cccd1188efc453c74b"
|
||||
|
||||
S = "${WORKDIR}/${ROS_SP}/${ROS_BPN}"
|
||||
S = "${WORKDIR}/git/${ROS_BPN}"
|
||||
|
||||
inherit catkin
|
||||
|
||||
|
|
Loading…
Reference in New Issue