From: "Richard Farina" <zerochaos@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-wireless/soapysdr/
Date: Tue, 4 Sep 2018 20:54:40 +0000 (UTC) [thread overview]
Message-ID: <1536094467.063f324eba15a918a5ea1a94f0878e2bc14a820c.zerochaos@gentoo> (raw)
commit: 063f324eba15a918a5ea1a94f0878e2bc14a820c
Author: Zero_Chaos <zerochaos <AT> gentoo <DOT> org>
AuthorDate: Tue Sep 4 20:30:37 2018 +0000
Commit: Richard Farina <zerochaos <AT> gentoo <DOT> org>
CommitDate: Tue Sep 4 20:54:27 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=063f324e
net-wireless/soapysdr: add plutosdr support
Package-Manager: Portage-2.3.48, Repoman-2.3.10
net-wireless/soapysdr/metadata.xml | 1 +
.../soapysdr/{soapysdr-0.6.1.ebuild => soapysdr-0.6.1-r1.ebuild} | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/net-wireless/soapysdr/metadata.xml b/net-wireless/soapysdr/metadata.xml
index 2d7ac62a7df..8b0393c48e0 100644
--- a/net-wireless/soapysdr/metadata.xml
+++ b/net-wireless/soapysdr/metadata.xml
@@ -13,6 +13,7 @@
<flag name="bladerf">Add support for bladerf hardware</flag>
<flag name="hackrf">Add support for hackrf hardware</flag>
<flag name="rtlsdr">Add support for rtlsdr hardware</flag>
+ <flag name="plutosdr">Add support for Analog Devices ADALM-PLUTO hardware</flag>
<flag name="uhd">Add support for Ettus USRP hardware</flag>
</use>
<upstream>
diff --git a/net-wireless/soapysdr/soapysdr-0.6.1.ebuild b/net-wireless/soapysdr/soapysdr-0.6.1-r1.ebuild
similarity index 92%
rename from net-wireless/soapysdr/soapysdr-0.6.1.ebuild
rename to net-wireless/soapysdr/soapysdr-0.6.1-r1.ebuild
index 0669ed4ac68..699b01529e7 100644
--- a/net-wireless/soapysdr/soapysdr-0.6.1.ebuild
+++ b/net-wireless/soapysdr/soapysdr-0.6.1-r1.ebuild
@@ -24,7 +24,7 @@ fi
LICENSE="Boost-1.0"
SLOT="0"
-IUSE="bladerf hackrf python rtlsdr uhd"
+IUSE="bladerf hackrf python rtlsdr plutosdr uhd"
REQUIRED_USE="python? ( ${PYTHON_REQUIRED_USE} )"
RDEPEND="python? ( ${PYTHON_DEPS} )"
@@ -34,6 +34,7 @@ DEPEND="${RDEPEND}
PDEPEND="bladerf? ( net-wireless/soapybladerf )
hackrf? ( net-wireless/soapyhackrf )
rtlsdr? ( net-wireless/soapyrtlsdr )
+ plutosdr? ( net-wireless/soapyplutosdr )
uhd? ( net-wireless/soapyuhd )"
src_configure() {
next reply other threads:[~2018-09-04 20:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 20:54 Richard Farina [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-24 19:06 [gentoo-commits] repo/gentoo:master commit in: net-wireless/soapysdr/ Arthur Zamarin
2024-12-08 5:23 Matt Jolly
2024-06-02 1:46 Sam James
2024-06-02 1:44 Sam James
2024-05-18 8:18 Arthur Zamarin
2023-08-19 13:41 Rick Farina
2023-08-19 13:41 Rick Farina
2023-08-19 13:41 Rick Farina
2023-04-06 2:18 Rick Farina
2023-04-04 19:56 Rick Farina
2023-04-04 19:56 Rick Farina
2022-07-13 6:15 Sam James
2022-06-10 13:03 Thomas Beierlein
2022-04-30 19:09 Marek Szuba
2021-06-10 3:37 Sam James
2020-12-04 3:16 Rick Farina
2020-08-14 23:22 Andreas Sturmlechner
2020-02-10 21:25 Michał Górny
2019-12-20 19:41 Rick Farina
2019-08-28 14:52 Rick Farina
2018-11-07 20:01 Rick Farina
2018-08-26 10:03 Christian Ruppert
2018-02-19 17:29 Richard Farina
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=1536094467.063f324eba15a918a5ea1a94f0878e2bc14a820c.zerochaos@gentoo \
--to=zerochaos@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