public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libcgroup/
Date: Thu,  3 Jan 2019 09:16:16 +0000 (UTC)	[thread overview]
Message-ID: <1546506898.a93b3a6f21c48494aba1a78f70ee1d94f9c1a8bb.vapier@gentoo> (raw)

commit:     a93b3a6f21c48494aba1a78f70ee1d94f9c1a8bb
Author:     Mike Frysinger <vapier <AT> chromium <DOT> org>
AuthorDate: Thu Jan  3 09:14:47 2019 +0000
Commit:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Thu Jan  3 09:14:58 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a93b3a6f

dev-libs/libcgroup: avoid building tests when USE=-test

Signed-off-by: Mike Frysinger <vapier <AT> gentoo.org>

 dev-libs/libcgroup/libcgroup-0.41-r5.ebuild | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/dev-libs/libcgroup/libcgroup-0.41-r5.ebuild b/dev-libs/libcgroup/libcgroup-0.41-r5.ebuild
index a4301a5acce..6c256390301 100644
--- a/dev-libs/libcgroup/libcgroup-0.41-r5.ebuild
+++ b/dev-libs/libcgroup/libcgroup-0.41-r5.ebuild
@@ -12,7 +12,7 @@ SRC_URI="mirror://sourceforge/project/libcg/${PN}/v${PV}/${P}.tar.bz2"
 LICENSE="LGPL-2.1"
 SLOT="0"
 KEYWORDS="amd64 arm ~ppc ~ppc64 x86"
-IUSE="+daemon elibc_musl pam static-libs +tools"
+IUSE="+daemon elibc_musl pam static-libs test +tools"
 
 RDEPEND="pam? ( virtual/pam )"
 
@@ -51,6 +51,11 @@ src_prepare() {
 		-i src/pam/Makefile.am || die "sed failed"
 	sed -e 's#/var/run#/run#g' -i configure.in || die "sed failed"
 
+	# If we're not running tests, don't bother building them.
+	if ! use test; then
+		sed -i '/^SUBDIRS/s:tests::' Makefile.am || die
+	fi
+
 	eautoreconf
 }
 


             reply	other threads:[~2019-01-03  9:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03  9:16 Mike Frysinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-09  7:15 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libcgroup/ Joonas Niilola
2023-12-08  8:51 Arthur Zamarin
2023-12-08  8:48 Arthur Zamarin
2023-12-08  8:48 Arthur Zamarin
2023-09-27  4:06 Sam James
2023-09-27  4:03 Sam James
2023-09-25  3:29 Sam James
2023-09-25  3:29 Sam James
2023-09-25  3:29 Sam James
2023-03-17 17:22 Sam James
2023-03-17 17:00 Sam James
2023-03-17 16:28 Arthur Zamarin
2023-03-17 16:12 Arthur Zamarin
2022-07-29  3:08 Sam James
2021-09-18 22:25 Anthony G. Basile
2021-08-15 21:06 Andreas Sturmlechner
2021-07-05 19:38 Marek Szuba
2021-05-04 19:13 Sam James
2021-05-01 18:11 Sam James
2021-05-01 18:11 Sam James
2021-05-01 17:13 Sam James
2019-10-12 18:58 Mikle Kolyada
2019-09-21  9:15 Michał Górny
2019-04-21  2:34 Anthony G. Basile
2019-04-16 12:48 Anthony G. Basile
2018-11-07  6:23 Anthony G. Basile
2018-08-23  0:39 Anthony G. Basile
2018-08-23  0:37 Anthony G. Basile
2018-08-23  0:28 Anthony G. Basile
2018-08-15 22:53 Anthony G. Basile
2018-04-21 11:15 Anthony G. Basile
2017-12-21 21:32 Anthony G. Basile
2017-12-21 21:32 Anthony G. Basile
2017-12-21 21:32 Anthony G. Basile
2016-10-10 13:28 Anthony G. Basile
2015-09-06 16:40 Anthony G. Basile
2015-09-06 15:49 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=1546506898.a93b3a6f21c48494aba1a78f70ee1d94f9c1a8bb.vapier@gentoo \
    --to=vapier@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