public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alexis Ballier" <aballier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ros/nav_core/
Date: Fri, 27 Jul 2018 10:56:36 +0000 (UTC)	[thread overview]
Message-ID: <1532683562.3d168b61ff2183540ee1e52d40e47943397c9db2.aballier@gentoo> (raw)

commit:     3d168b61ff2183540ee1e52d40e47943397c9db2
Author:     Alexis Ballier <aballier <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 27 09:09:20 2018 +0000
Commit:     Alexis Ballier <aballier <AT> gentoo <DOT> org>
CommitDate: Fri Jul 27 09:26:02 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3d168b61

dev-ros/nav_core: Bump to 1.16.0.

Package-Manager: Portage-2.3.43, Repoman-2.3.10

 dev-ros/nav_core/Manifest               |  1 +
 dev-ros/nav_core/nav_core-1.16.0.ebuild | 22 ++++++++++++++++++++++
 2 files changed, 23 insertions(+)

diff --git a/dev-ros/nav_core/Manifest b/dev-ros/nav_core/Manifest
index 1ff34582242..e2d2b2ee457 100644
--- a/dev-ros/nav_core/Manifest
+++ b/dev-ros/nav_core/Manifest
@@ -1 +1,2 @@
 DIST navigation-1.15.2.tar.gz 348985 BLAKE2B 866779425828b1e4c3a044654ae41f33643646ca70cf6841f23bce265add2c420bf0934a41a6b29fa65fc421228a31dc15e9fb0f6cc4295ce12adbbb627b43d4 SHA512 582422756b31b4d83e929e3c723e7205e772b9775fcf618c9bd5d3c54af1f20e9bc8a0143626750c0c3cffeb0cbea8f8706b7e66f62dc037cfe12b05f23ee142
+DIST navigation-1.16.0.tar.gz 336708 BLAKE2B 74fdc7c3afb00bfbded011678c90b22cc95fe45b126c9a8a4bb9a80f8676ed0ade32e02ad77ec643f167d9719e71347750b6f7993f61cf743fc018d1412436d6 SHA512 ee6336627c2e095ef089534c19b7258f394858a6c04ad49b3aa6e1d0acca67c245c2743f04752be137864dba216c3aa38e34c3e40e3db7839308be3adbc808d6

diff --git a/dev-ros/nav_core/nav_core-1.16.0.ebuild b/dev-ros/nav_core/nav_core-1.16.0.ebuild
new file mode 100644
index 00000000000..5001237ab34
--- /dev/null
+++ b/dev-ros/nav_core/nav_core-1.16.0.ebuild
@@ -0,0 +1,22 @@
+# Copyright 1999-2018 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=5
+ROS_REPO_URI="https://github.com/ros-planning/navigation"
+ROS_SUBDIR=${PN}
+KEYWORDS="~amd64 ~arm"
+
+inherit ros-catkin
+
+DESCRIPTION="Common interfaces for navigation specific robot actions"
+LICENSE="BSD"
+SLOT="0"
+IUSE=""
+
+RDEPEND="
+	dev-ros/costmap_2d
+	dev-ros/geometry_msgs[${CATKIN_MESSAGES_CXX_USEDEP}]
+	dev-ros/std_msgs[${CATKIN_MESSAGES_CXX_USEDEP}]
+	dev-ros/tf2_ros
+"
+DEPEND="${RDEPEND}"


             reply	other threads:[~2018-07-27 10:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27 10:56 Alexis Ballier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-10 16:02 [gentoo-commits] repo/gentoo:master commit in: dev-ros/nav_core/ Alexis Ballier
2020-07-10 16:02 Alexis Ballier
2020-07-10 16:02 Alexis Ballier
2020-05-18 15:18 Alexis Ballier
2019-12-11 16:12 Alexis Ballier
2018-08-04 18:46 Alexis Ballier
2018-07-31 13:09 Alexis Ballier
2018-07-27 10:56 Alexis Ballier
2018-07-27 10:56 Alexis Ballier
2018-03-25 13:48 Alexis Ballier
2017-08-23  7:30 Alexis Ballier
2017-08-15  6:25 Alexis Ballier
2016-05-23  9:01 Alexis Ballier
2015-11-01 10:07 Alexis Ballier
2015-09-30 12:04 Alexis Ballier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1532683562.3d168b61ff2183540ee1e52d40e47943397c9db2.aballier@gentoo \
    --to=aballier@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox