From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-p2p/bitcoin-qt/
Date: Thu, 5 Jan 2023 05:05:38 +0000 (UTC) [thread overview]
Message-ID: <1672893639.246e628607d258482485088ff164a84f480f7caa.sam@gentoo> (raw)
commit: 246e628607d258482485088ff164a84f480f7caa
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 5 04:40:39 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jan 5 04:40:39 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=246e6286
net-p2p/bitcoin-qt: add note re bundled dev-libs/univalue
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-p2p/bitcoin-qt/bitcoin-qt-24.0.1.ebuild | 3 +++
1 file changed, 3 insertions(+)
diff --git a/net-p2p/bitcoin-qt/bitcoin-qt-24.0.1.ebuild b/net-p2p/bitcoin-qt/bitcoin-qt-24.0.1.ebuild
index a08802221ce1..76fdba8ff317 100644
--- a/net-p2p/bitcoin-qt/bitcoin-qt-24.0.1.ebuild
+++ b/net-p2p/bitcoin-qt/bitcoin-qt-24.0.1.ebuild
@@ -24,6 +24,9 @@ REQUIRED_USE="
berkdb? ( wallet )
wallet? ( || ( berkdb sqlite ) )
"
+# dev-libs/univalue is now bundled as upstream dropped support for system copy
+# and their version in the Bitcoin repo has deviated a fair bit from upstream.
+# Upstream also seems very inactive.
RDEPEND="
dev-libs/boost:=
>=dev-libs/libsecp256k1-0.2.0:=[recovery,schnorr]
next reply other threads:[~2023-01-05 5:05 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 5:05 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-31 2:23 [gentoo-commits] repo/gentoo:master commit in: net-p2p/bitcoin-qt/ Sam James
2023-10-24 9:14 Joonas Niilola
2023-10-19 17:06 Florian Schmaus
2023-03-19 4:21 Sam James
2023-01-04 14:28 Arthur Zamarin
2023-01-04 9:42 Sam James
2022-09-30 23:24 Sam James
2022-09-04 13:03 David Seifert
2022-01-15 8:30 Joonas Niilola
2021-12-17 8:13 Florian Schmaus
2021-11-18 6:55 Joonas Niilola
2021-07-11 14:42 Craig Andrews
2021-07-10 2:21 Georgy Yakovlev
2021-07-10 1:19 Craig Andrews
2021-05-28 2:27 Sam James
2021-02-07 9:03 Joonas Niilola
2021-01-21 23:23 Sam James
2020-08-29 13:23 Sam James
2020-08-19 0:54 Craig Andrews
2020-06-17 1:52 Craig Andrews
2020-03-07 21:15 Craig Andrews
2020-03-07 21:15 Craig Andrews
2020-03-07 21:15 Craig Andrews
2019-08-07 16:33 Craig Andrews
2018-09-25 11:17 Agostino Sarubbo
2018-09-21 12:40 Virgil Dupras
2018-04-07 20:49 Andreas Sturmlechner
2018-04-06 20:56 Matt Turner
2018-04-04 23:04 Andreas Sturmlechner
2018-03-28 19:09 Matt Turner
2018-03-18 14:17 Andreas Sturmlechner
2018-03-18 13:57 Mikle Kolyada
2018-02-22 9:05 Agostino Sarubbo
2018-01-28 23:19 Andreas Sturmlechner
2018-01-26 23:24 Thomas Deutschmann
2018-01-19 18:40 Andreas Sturmlechner
2018-01-09 15:51 Ulrich Müller
2017-12-31 16:20 Mike Gilbert
2017-04-08 21:29 Patrice Clement
2017-03-11 18:33 Anthony G. Basile
2016-12-20 9:08 Agostino Sarubbo
2016-12-19 19:56 Tobias Klausmann
2016-11-09 3:37 Anthony G. Basile
2016-11-09 3:37 Anthony G. Basile
2016-07-31 20:27 Anthony G. Basile
2015-11-27 20:01 Anthony G. Basile
2015-10-01 14:21 Michael Palimaka
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=1672893639.246e628607d258482485088ff164a84f480f7caa.sam@gentoo \
--to=sam@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