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/hector_map_tools/
Date: Tue,  5 Jan 2021 20:03:09 +0000 (UTC)	[thread overview]
Message-ID: <1609876977.47cb807f1fa069a49f74731e04b63ab8027a3abb.aballier@gentoo> (raw)

commit:     47cb807f1fa069a49f74731e04b63ab8027a3abb
Author:     Alexis Ballier <aballier <AT> gentoo <DOT> org>
AuthorDate: Tue Jan  5 19:46:32 2021 +0000
Commit:     Alexis Ballier <aballier <AT> gentoo <DOT> org>
CommitDate: Tue Jan  5 20:02:57 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=47cb807f

dev-ros/hector_map_tools: Bump to 0.5.0.

Package-Manager: Portage-3.0.8, Repoman-3.0.2
Signed-off-by: Alexis Ballier <aballier <AT> gentoo.org>

 dev-ros/hector_map_tools/Manifest                    |  1 +
 .../hector_map_tools/hector_map_tools-0.5.0.ebuild   | 20 ++++++++++++++++++++
 2 files changed, 21 insertions(+)

diff --git a/dev-ros/hector_map_tools/Manifest b/dev-ros/hector_map_tools/Manifest
index 703025b7231..c1392287757 100644
--- a/dev-ros/hector_map_tools/Manifest
+++ b/dev-ros/hector_map_tools/Manifest
@@ -1 +1,2 @@
 DIST hector_slam-0.4.1.tar.gz 66772 BLAKE2B ad6f5596ea1fca2ed68017534280a4d622179de8df4c039e95f3e87a0e591212944d65e4d507194eb33584f7f55cba4fe398b19f5a22bfb3afce1b2406d1635d SHA512 bd0932971114f13c41c6e346756f2c95cc0a9a011d11202792a6f837757a144355e05c3e7ed1afa574b743166a78f1a7855c5693b0c57378611e50c386c2483e
+DIST hector_slam-0.5.0.tar.gz 160320 BLAKE2B 9109b81740296aada8b0987d153774ac547cf063546973e8034849a5c81117c10047c12ca65f15feae5355c35a6e746cbf0ab8fa2089d282beb1f7aa06528254 SHA512 d9d7e0e7de96330358bcd98de2083ee67e0d232d6758599291607951696aef5dd93b335252448ddec59202627f69fd5a9122c0f3a2829744b4b6417906aab3ed

diff --git a/dev-ros/hector_map_tools/hector_map_tools-0.5.0.ebuild b/dev-ros/hector_map_tools/hector_map_tools-0.5.0.ebuild
new file mode 100644
index 00000000000..85ada002eff
--- /dev/null
+++ b/dev-ros/hector_map_tools/hector_map_tools-0.5.0.ebuild
@@ -0,0 +1,20 @@
+# Copyright 1999-2021 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+ROS_REPO_URI="https://github.com/tu-darmstadt-ros-pkg/hector_slam"
+KEYWORDS="~amd64 ~arm"
+ROS_SUBDIR=${PN}
+
+inherit ros-catkin
+
+DESCRIPTION="Functions related to accessing information from OccupancyGridMap maps"
+LICENSE="BSD"
+SLOT="0"
+IUSE=""
+
+RDEPEND=""
+DEPEND="${RDEPEND}
+	dev-ros/nav_msgs[${CATKIN_MESSAGES_CXX_USEDEP}]
+	dev-cpp/eigen:3
+"


             reply	other threads:[~2021-01-05 20:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 20:03 Alexis Ballier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-16 16:31 [gentoo-commits] repo/gentoo:master commit in: dev-ros/hector_map_tools/ Alexis Ballier
2020-07-16 16:31 Alexis Ballier
2020-04-14 12:57 Alexis Ballier
2020-04-14 12:57 Alexis Ballier
2019-12-13 12:16 Alexis Ballier
2019-12-13 12:16 Alexis Ballier
2016-06-28 13:56 Alexis Ballier
2015-11-10  6:52 Alexis Ballier
2015-09-28 12:58 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=1609876977.47cb807f1fa069a49f74731e04b63ab8027a3abb.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