public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Victor Skovorodnikov" <victor3.14@yandex.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: net-p2p/dogecoin-qt/
Date: Thu, 20 Jul 2023 18:28:09 +0000 (UTC)	[thread overview]
Message-ID: <1689877682.ff90fe8035bde70313c1102017d1da39575cd0e4.victor3.14@gentoo> (raw)

commit:     ff90fe8035bde70313c1102017d1da39575cd0e4
Author:     Victor Skovorodnikov <victor3.14 <AT> yandex <DOT> com>
AuthorDate: Thu Jul 20 18:26:27 2023 +0000
Commit:     Victor Skovorodnikov <victor3.14 <AT> yandex <DOT> com>
CommitDate: Thu Jul 20 18:28:02 2023 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=ff90fe80

net-p2p/dogecoin-qt: added REQUIRED_USE constraint for dogecoind option

Signed-off-by: Victor Skovorodnikov <victor3.14 <AT> yandex.com>

 net-p2p/dogecoin-qt/dogecoin-qt-1.14.6.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/net-p2p/dogecoin-qt/dogecoin-qt-1.14.6.ebuild b/net-p2p/dogecoin-qt/dogecoin-qt-1.14.6.ebuild
index d4acd2cd3..f4843ac9e 100644
--- a/net-p2p/dogecoin-qt/dogecoin-qt-1.14.6.ebuild
+++ b/net-p2p/dogecoin-qt/dogecoin-qt-1.14.6.ebuild
@@ -13,6 +13,7 @@ SLOT="0"
 DB_VER="5.3"
 KEYWORDS="~amd64"
 IUSE="cpu_flags_x86_avx2 dogecoind tests utils +wallet +prune zmq"
+REQUIRED_USE="dogecoind? ( utils )"
 DOGEDIR="/opt/${PN}"
 DEPEND="
 	sys-libs/db:"${DB_VER}"=[cxx]


             reply	other threads:[~2023-07-20 18:28 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 18:28 Victor Skovorodnikov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-18  8:43 [gentoo-commits] repo/proj/guru:dev commit in: net-p2p/dogecoin-qt/ Victor Skovorodnikov
2025-02-18  6:46 Joe Kappus
2025-02-18  6:46 Joe Kappus
2025-02-18  6:46 Joe Kappus
2024-12-02 18:21 Victor Skovorodnikov
2024-12-01 16:41 Victor Skovorodnikov
2024-09-01 15:16 Victor Skovorodnikov
2024-08-12 16:26 Victor Skovorodnikov
2024-08-10 17:57 Victor Skovorodnikov
2024-08-09 15:40 Victor Skovorodnikov
2024-08-07 21:44 Victor Skovorodnikov
2024-08-03 14:40 Victor Skovorodnikov
2024-07-07 16:15 Victor Skovorodnikov
2024-05-26 20:24 Victor Skovorodnikov
2024-03-02 17:34 Victor Skovorodnikov
2024-03-02  3:37 Victor Skovorodnikov
2024-03-02  3:23 Victor Skovorodnikov
2024-02-28  0:09 Victor Skovorodnikov
2024-02-27 20:13 Victor Skovorodnikov
2024-02-27 16:52 Victor Skovorodnikov
2024-02-27 16:52 Victor Skovorodnikov
2024-02-11 23:42 Victor Skovorodnikov
2023-10-27 22:13 Victor Skovorodnikov
2023-09-25 19:44 Victor Skovorodnikov
2023-07-24 20:26 Anna Vyalkova
2023-07-24 20:26 Anna Vyalkova
2023-07-24 19:47 Victor Skovorodnikov
2023-07-24 19:15 Victor Skovorodnikov
2023-07-18 22:03 Victor Skovorodnikov
2023-07-17 21:30 Victor Skovorodnikov
2023-07-17 21:30 Victor Skovorodnikov
2023-07-16  0:27 Victor Skovorodnikov
2023-07-14 16:47 Victor Skovorodnikov
2023-07-13 23:41 Victor Skovorodnikov
2023-07-13  1:36 Victor Skovorodnikov
2023-07-12  4:58 Viorel Munteanu
2023-07-11 23:59 Victor Skovorodnikov
2023-07-11 23:28 Victor Skovorodnikov
2023-07-11  2:03 Victor Skovorodnikov
2023-07-06 22:36 Victor Skovorodnikov
2023-07-06 22:36 Victor Skovorodnikov
2023-07-06 18:48 Victor Skovorodnikov

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=1689877682.ff90fe8035bde70313c1102017d1da39575cd0e4.victor3.14@gentoo \
    --to=victor3.14@yandex.com \
    --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