public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Quincy Fleming" <quincyf467@protonmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: app-admin/hardinfo2/
Date: Sat,  7 Sep 2024 20:59:59 +0000 (UTC)	[thread overview]
Message-ID: <1725742759.e46f5301e6dfe81724e01956baacfbf19e0d9a32.quincyf467@gentoo> (raw)

commit:     e46f5301e6dfe81724e01956baacfbf19e0d9a32
Author:     Quincy Fleming <quincyf467 <AT> protonmail <DOT> com>
AuthorDate: Sat Sep  7 20:59:19 2024 +0000
Commit:     Quincy Fleming <quincyf467 <AT> protonmail <DOT> com>
CommitDate: Sat Sep  7 20:59:19 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=e46f5301

app-admin/hardinfo2: add 2.1.14, drop 2.1.11-r1

Signed-off-by: Quincy Fleming <quincyf467 <AT> protonmail.com>

 app-admin/hardinfo2/Manifest                                            | 2 +-
 .../hardinfo2/{hardinfo2-2.1.11-r1.ebuild => hardinfo2-2.1.14.ebuild}   | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/app-admin/hardinfo2/Manifest b/app-admin/hardinfo2/Manifest
index a2abd8c9d..22e557b69 100644
--- a/app-admin/hardinfo2/Manifest
+++ b/app-admin/hardinfo2/Manifest
@@ -1 +1 @@
-DIST hardinfo2-2.1.11.tar.gz 5806488 BLAKE2B 866b5e179e07c781de67b7169d03763059c1a8a5c974e8ffd3332c2d639f28dac0837138bcc1dacec88f8d94dcc1654d6383128ea21961cfb9a3b16d57205913 SHA512 639d2d02cd6320d56c5f078f69ff43c0bd74844ecc73df05ee205070732e4a6aeb5e169b78a883c83734be69b547f0736522b2fb6377a0e4a59c07be0a1c8c43
+DIST hardinfo2-2.1.14.tar.gz 5990753 BLAKE2B 5ac04a6d4dc07bf4fd99a86ff9306699e8e68499638fbe9d07ffb48fb0f40ee79f1e11b6be3337497bdee9873ec3f2b46791adbff5e24aacfab328dd31dec8c0 SHA512 0c6f62b07bc52c9e07c6eff66c485962e03f019cf566d0954e3accb537a27ff49765ed87fea5112543db6039439bb5402b3362899d9706fc510510fbf24f50cf

diff --git a/app-admin/hardinfo2/hardinfo2-2.1.11-r1.ebuild b/app-admin/hardinfo2/hardinfo2-2.1.14.ebuild
similarity index 98%
rename from app-admin/hardinfo2/hardinfo2-2.1.11-r1.ebuild
rename to app-admin/hardinfo2/hardinfo2-2.1.14.ebuild
index 3b81691bd..a94c26024 100644
--- a/app-admin/hardinfo2/hardinfo2-2.1.11-r1.ebuild
+++ b/app-admin/hardinfo2/hardinfo2-2.1.14.ebuild
@@ -44,6 +44,7 @@ BDEPEND="virtual/pkgconfig"
 src_configure() {
 	local mycmakeargs=(
 		-DHARDINFO2_GTK3=$(usex gtk3)
+		-DHARDINFO2_QT5=0
 	)
 	cmake_src_configure
 }


             reply	other threads:[~2024-09-07 21:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-07 20:59 Quincy Fleming [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-25 17:19 [gentoo-commits] repo/proj/guru:dev commit in: app-admin/hardinfo2/ Quincy Fleming
2025-02-25 17:17 Quincy Fleming
2024-11-28  9:10 Quincy Fleming
2024-11-27 11:31 Quincy Fleming
2024-11-06 20:46 Quincy Fleming
2024-11-06 20:45 Quincy Fleming
2024-11-01  0:23 Quincy Fleming
2024-11-01  0:21 Quincy Fleming
2024-10-02 23:31 Quincy Fleming
2024-08-03  6:11 Quincy Fleming
2024-05-28 19:53 Quincy Fleming
2024-05-28 19:02 Quincy Fleming
2024-05-28 18:45 Quincy Fleming
2024-05-27  1:47 Quincy Fleming
2024-05-27  1:47 Quincy Fleming
2024-05-27  1:47 Quincy Fleming

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=1725742759.e46f5301e6dfe81724e01956baacfbf19e0d9a32.quincyf467@gentoo \
    --to=quincyf467@protonmail.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