From: "Florian Schmaus" <flow@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-wireless/bluez-tools/
Date: Mon, 3 Jan 2022 18:43:10 +0000 (UTC) [thread overview]
Message-ID: <1641235275.93fc32ddc98538d75347b756f0d508c454a48a9c.flow@gentoo> (raw)
commit: 93fc32ddc98538d75347b756f0d508c454a48a9c
Author: Olivier Laurantin <olivier.laurantin <AT> laposte <DOT> net>
AuthorDate: Sat Jan 1 10:38:49 2022 +0000
Commit: Florian Schmaus <flow <AT> gentoo <DOT> org>
CommitDate: Mon Jan 3 18:41:15 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=93fc32dd
net-wireless/bluez-tools: version bump
Update to latest git commit
Package-Manager: Portage-3.0.28, Repoman-3.0.3
Signed-off-by: Olivier Laurantin <olivier.laurantin <AT> laposte.net>
Signed-off-by: Florian Schmaus <flow <AT> gentoo.org>
net-wireless/bluez-tools/Manifest | 1 +
.../bluez-tools/bluez-tools-0_p20201025.ebuild | 31 ++++++++++++++++++++++
2 files changed, 32 insertions(+)
diff --git a/net-wireless/bluez-tools/Manifest b/net-wireless/bluez-tools/Manifest
index d2efe655a73e..3d34b1d3f9ec 100644
--- a/net-wireless/bluez-tools/Manifest
+++ b/net-wireless/bluez-tools/Manifest
@@ -1 +1,2 @@
DIST bluez-tools-0_p20161212.tar.gz 126613 BLAKE2B 474393862049a893280eeb0b7f466a1b1165a14d0ab33cbd9d3ca805a15eef237761aa3038423de85280bcaaf1385c3c7ab313d4cc3199f284aba86d8e5ed16e SHA512 ab5dd4a223348aab29fae22f552afae989b74d56c3fa46fd5587c100d63309649a10a87591bc040082545f45b7bb95360fcf6a48812012edbdb93570b0e166f7
+DIST bluez-tools-0_p20201025.tar.gz 126646 BLAKE2B 6deea6a12ee1050cbe12592fe202be60f032a7ee9a8f790537ef24c3a2562d90abf88f69690e6dd53f16841a256fc82dcfb078b2d708531ca6c50f63b6e84274 SHA512 631dfa7ee7e1bfe487db90f9df692c4136d6258ddd34cda269e3a9538a3c8fe8bad3bac595e57d74789df2da4e15fa0ca7b83374e7f6457695701852b3744b12
diff --git a/net-wireless/bluez-tools/bluez-tools-0_p20201025.ebuild b/net-wireless/bluez-tools/bluez-tools-0_p20201025.ebuild
new file mode 100644
index 000000000000..755069585081
--- /dev/null
+++ b/net-wireless/bluez-tools/bluez-tools-0_p20201025.ebuild
@@ -0,0 +1,31 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+inherit autotools
+
+DESCRIPTION="A set of tools to manage bluetooth devices for linux"
+HOMEPAGE="https://github.com/khvzak/bluez-tools"
+COMMIT="f65321736475429316f07ee94ec0deac8e46ec4a"
+SRC_URI="https://github.com/khvzak/${PN}/archive/${COMMIT}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="GPL-2+"
+SLOT="0"
+KEYWORDS="~amd64 ~arm ~arm64 ~riscv ~x86"
+IUSE=""
+
+RDEPEND="dev-libs/dbus-glib
+ dev-libs/glib:2
+ net-wireless/bluez[obex]
+ sys-libs/readline:0"
+DEPEND="${RDEPEND}"
+
+DOCS=( AUTHORS README )
+
+S="${WORKDIR}/${PN}-${COMMIT}"
+
+src_prepare() {
+ default
+ eautoreconf
+}
next reply other threads:[~2022-01-03 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 18:43 Florian Schmaus [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-02 10:04 [gentoo-commits] repo/gentoo:master commit in: net-wireless/bluez-tools/ Yixun Lan
2020-09-15 14:20 Joonas Niilola
2017-09-03 8:09 Alexis Ballier
2017-07-24 17:52 Markus Meier
2017-06-25 19:47 Kristian Fiskerstrand
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=1641235275.93fc32ddc98538d75347b756f0d508c454a48a9c.flow@gentoo \
--to=flow@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