public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rui Huang" <vowstar@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: sys-process/nvtop/
Date: Sun, 14 Jun 2020 11:03:43 +0000 (UTC)	[thread overview]
Message-ID: <1592132558.147fbf6bcc8a3972080db01d7a7837d4b34546d7.vowstar@gentoo> (raw)

commit:     147fbf6bcc8a3972080db01d7a7837d4b34546d7
Author:     Huang Rui <vowstar <AT> gmail <DOT> com>
AuthorDate: Sun Jun 14 11:02:18 2020 +0000
Commit:     Rui Huang <vowstar <AT> gmail <DOT> com>
CommitDate: Sun Jun 14 11:02:38 2020 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=147fbf6b

sys-process/nvtop: use cmake eclass replace cmake-utils

make-utils eclass will be deprecated soon

Package-Manager: Portage-2.3.100, Repoman-2.3.22
Signed-off-by: Huang Rui <vowstar <AT> gmail.com>

 sys-process/nvtop/nvtop-1.0.0.ebuild | 4 ++--
 sys-process/nvtop/nvtop-9999.ebuild  | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/sys-process/nvtop/nvtop-1.0.0.ebuild b/sys-process/nvtop/nvtop-1.0.0.ebuild
index 5a831a1..cf47220 100644
--- a/sys-process/nvtop/nvtop-1.0.0.ebuild
+++ b/sys-process/nvtop/nvtop-1.0.0.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=7
 
-inherit cmake-utils
+inherit cmake
 
 DESCRIPTION="NVIDIA GPUs htop like monitoring tool"
 HOMEPAGE="https://github.com/Syllo/nvtop"
@@ -49,5 +49,5 @@ src_configure() {
 		${CMAKE_CONF}
 	)
 
-	cmake-utils_src_configure
+	cmake_src_configure
 }

diff --git a/sys-process/nvtop/nvtop-9999.ebuild b/sys-process/nvtop/nvtop-9999.ebuild
index 42b38e8..02eab10 100644
--- a/sys-process/nvtop/nvtop-9999.ebuild
+++ b/sys-process/nvtop/nvtop-9999.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=7
 
-inherit cmake-utils
+inherit cmake
 
 DESCRIPTION="NVIDIA GPUs htop like monitoring tool"
 HOMEPAGE="https://github.com/Syllo/nvtop"
@@ -48,5 +48,5 @@ src_configure() {
 		${CMAKE_CONF}
 	)
 
-	cmake-utils_src_configure
+	cmake_src_configure
 }


             reply	other threads:[~2020-06-14 11:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14 11:03 Rui Huang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-14  3:34 [gentoo-commits] repo/proj/guru:dev commit in: sys-process/nvtop/ Rui Huang
2024-12-13  9:59 Rui Huang
2024-12-13  7:59 Rui Huang
2024-12-13  7:59 Rui Huang
2024-11-30 12:29 Filip Kobierski
2024-02-09 17:16 Haelwenn Monnier
2024-01-12  5:47 YiFei Zhu
2023-03-31  4:40 Rui Huang
2023-03-31  4:38 Rui Huang
2022-10-25  2:47 Carlos Eduardo
2022-09-06  3:25 Rui Huang
2022-09-06  2:50 Rui Huang
2022-09-06  2:50 Rui Huang
2022-09-06  2:50 Rui Huang
2022-07-08  4:53 Rui Huang
2022-07-08  4:53 Rui Huang
2022-04-25  8:26 Rui Huang
2022-04-24  4:08 Rui Huang
2022-02-07 15:51 Rui Huang
2021-11-08 13:08 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-11-08 13:08 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2021-08-03  8:55 Andrew Ammerlaan
2021-07-28  2:36 Rui Huang
2021-07-28  2:34 Rui Huang
2021-05-31  3:01 Rui Huang
2021-05-31  3:01 Rui Huang
2021-01-01  9:55 Rui Huang
2020-12-04 19:21 Rui Huang
2020-12-04 19:21 Rui Huang
2020-06-13 17:09 Rui Huang
2020-06-13 15:36 Rui Huang
2020-06-13 15:36 Rui Huang
2020-06-13 15:28 Rui Huang

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=1592132558.147fbf6bcc8a3972080db01d7a7837d4b34546d7.vowstar@gentoo \
    --to=vowstar@gmail.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