public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/grs/
Date: Tue, 23 Feb 2016 00:46:02 +0000 (UTC)	[thread overview]
Message-ID: <1456188942.3faadaff44e4a25f13c271c323c51365f3109bee.blueness@gentoo> (raw)

commit:     3faadaff44e4a25f13c271c323c51365f3109bee
Author:     Anthony G. Basile <blueness <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 23 00:55:25 2016 +0000
Commit:     Anthony G. Basile <blueness <AT> gentoo <DOT> org>
CommitDate: Tue Feb 23 00:55:42 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3faadaff

app-portage/grs: check kernel config for CGROUPS

Package-Manager: portage-2.2.26

 app-portage/grs/grs-9999.ebuild | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/app-portage/grs/grs-9999.ebuild b/app-portage/grs/grs-9999.ebuild
index 7eb8426..9f02750 100644
--- a/app-portage/grs/grs-9999.ebuild
+++ b/app-portage/grs/grs-9999.ebuild
@@ -1,9 +1,11 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Id$
 
 EAPI="5"
 
+inherit linux-info
+
 PYTHON_COMPAT=( python3_4 )
 
 inherit distutils-r1
@@ -38,6 +40,12 @@ RDEPEND="
 		sys-kernel/genkernel-next
 	)"
 
+pkg_setup() {
+	linux-info_pkg_setup
+	CONFIG_CHECK="~CGROUPS"
+	ERROR_CGROUPS="WARNING: grsrun requires CONFIG_CGROUPS enabled in the kernel."
+}
+
 src_install() {
 	distutils-r1_src_install
 	echo "CONFIG_PROTECT=\"/etc/grs/systems.conf\"" > "${T}"/20grs


             reply	other threads:[~2016-02-23  0:46 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23  0:46 Anthony G. Basile [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-22 15:28 [gentoo-commits] repo/gentoo:master commit in: app-portage/grs/ Anthony G. Basile
2024-06-10 18:16 Anthony G. Basile
2023-03-06 18:07 Anthony G. Basile
2023-01-11  8:07 Sam James
2022-08-01 17:05 Anthony G. Basile
2022-07-25 13:38 Anthony G. Basile
2022-07-21 16:21 Anthony G. Basile
2022-07-18 20:02 Anthony G. Basile
2021-09-24 11:10 Anthony G. Basile
2021-08-05  6:39 Anthony G. Basile
2020-12-18  9:00 Michał Górny
2020-06-05 15:46 Anthony G. Basile
2020-06-05 15:46 Anthony G. Basile
2019-12-26 17:02 Anthony G. Basile
2019-05-18 10:02 Michał Górny
2019-04-20 18:13 Anthony G. Basile
2019-04-16 12:53 Anthony G. Basile
2018-12-06 11:16 Anthony G. Basile
2018-11-14 23:00 Anthony G. Basile
2018-11-14 22:22 Anthony G. Basile
2018-11-07  6:23 Anthony G. Basile
2018-11-07  6:23 Anthony G. Basile
2018-03-21 18:12 Michał Górny
2018-01-20 13:54 Anthony G. Basile
2018-01-15 19:14 Anthony G. Basile
2018-01-15 12:27 Anthony G. Basile
2018-01-15  1:30 Anthony G. Basile
2018-01-14 17:37 Anthony G. Basile
2018-01-14 11:43 Anthony G. Basile
2018-01-14  9:49 Anthony G. Basile
2017-12-27 17:23 Anthony G. Basile
2017-12-27 17:21 Anthony G. Basile
2017-12-27 17:18 Anthony G. Basile
2017-12-27  8:03 Anthony G. Basile
2017-12-25 14:43 David Seifert
2017-04-22  9:56 Pacho Ramos
2016-03-07  0:11 Anthony G. Basile
2016-03-07  0:11 Anthony G. Basile
2016-02-23  1:50 Anthony G. Basile
2016-02-23  1:30 Anthony G. Basile
2016-01-09 21:22 Anthony G. Basile
2016-01-09 21:22 Anthony G. Basile
2015-12-09 17:02 Anthony G. Basile
2015-12-09 17:02 Anthony G. Basile
2015-10-13 21:57 Anthony G. Basile
2015-09-25  1:03 Anthony G. Basile
2015-09-22 19:34 Anthony G. Basile
2015-09-22 19:34 Anthony G. Basile
2015-08-13 13:44 Anthony G. Basile
2015-08-12  0:06 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=1456188942.3faadaff44e4a25f13c271c323c51365f3109bee.blueness@gentoo \
    --to=blueness@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