public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libgpiod/
Date: Fri,  9 Sep 2022 09:15:49 +0000 (UTC)	[thread overview]
Message-ID: <1662714936.8ba1b62c7bd0698c5b58f4bf371345bfeea2e958.sam@gentoo> (raw)

commit:     8ba1b62c7bd0698c5b58f4bf371345bfeea2e958
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Sep  9 09:15:12 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Sep  9 09:15:36 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8ba1b62c

dev-libs/libgpiod: add missing test deps

Not worrying about old version as multilib got dropped.

Closes: https://bugs.gentoo.org/702568
Closes: https://bugs.gentoo.org/865197
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-libs/libgpiod/libgpiod-1.6.3-r4.ebuild | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/dev-libs/libgpiod/libgpiod-1.6.3-r4.ebuild b/dev-libs/libgpiod/libgpiod-1.6.3-r4.ebuild
index 98464819a577..cf58ecdba373 100644
--- a/dev-libs/libgpiod/libgpiod-1.6.3-r4.ebuild
+++ b/dev-libs/libgpiod/libgpiod-1.6.3-r4.ebuild
@@ -19,6 +19,14 @@ RESTRICT="!test? ( test )"
 #  --enable-tests          enable libgpiod tests [default=no]
 #  --enable-bindings-cxx   enable C++ bindings [default=no]
 #  --enable-bindings-python
+DEPEND="
+	test? (
+		>=dev-libs/glib-2.50
+		>=sys-apps/kmod-18
+		>=sys-apps/util-linux-2.33.1
+		>=virtual/libudev-215
+	)
+"
 
 pkg_setup() {
 	CONFIG_CHECK="~GPIO_CDEV_V1"


             reply	other threads:[~2022-09-09  9:15 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  9:15 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-01 12:36 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libgpiod/ Yixun Lan
2025-04-01 12:36 Yixun Lan
2025-03-04  1:49 Yixun Lan
2024-11-01  0:49 Yixun Lan
2024-11-01  0:49 Yixun Lan
2024-08-12 10:40 Yixun Lan
2024-05-15 13:29 Yixun Lan
2024-05-15 12:49 Sam James
2024-05-15 12:10 Sam James
2024-05-15 12:10 Sam James
2024-05-15 12:10 Sam James
2024-05-15 11:18 Yixun Lan
2024-05-15 11:18 Yixun Lan
2024-03-23  2:18 Yixun Lan
2024-03-23  1:15 Yixun Lan
2023-11-23 12:32 Yixun Lan
2023-09-22  5:53 Yixun Lan
2023-09-22  5:53 Yixun Lan
2023-09-22  5:53 Yixun Lan
2022-10-25 17:57 Sam James
2022-10-25 17:55 Sam James
2022-10-25 17:55 Sam James
2022-10-25 11:18 Sam James
2022-10-25 11:18 Sam James
2022-10-25 11:06 Sam James
2022-09-09  9:25 Sam James
2022-09-09  9:25 Sam James
2022-09-09  9:25 Sam James
2022-08-16 15:57 Anthony G. Basile
2022-08-16 14:12 Anthony G. Basile
2022-07-28 14:14 Sam James
2022-07-21 14:54 Anthony G. Basile
2021-09-24 17:08 Anthony G. Basile
2021-09-24 17:08 Anthony G. Basile
2021-08-10 12:43 Marek Szuba
2021-01-09 10:36 Sam James
2020-06-09 13:53 Agostino Sarubbo
2020-06-09 13:47 Agostino Sarubbo
2020-06-09 13:45 Agostino Sarubbo
2020-06-09  4:23 Mart Raudsepp
2019-10-03 14:30 Anthony G. Basile
2019-04-21  3:05 Anthony G. Basile
2018-12-08 23:57 Anthony G. Basile
2018-09-16 10:29 Anthony G. Basile
2018-09-16 10:29 Anthony G. Basile
2018-04-06 14:59 Anthony G. Basile

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=1662714936.8ba1b62c7bd0698c5b58f4bf371345bfeea2e958.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