From: "Ronny Gutbrod" <gentoo@tastytea.de>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: gnome-extra/extension-manager/
Date: Thu, 24 Feb 2022 11:10:18 +0000 (UTC) [thread overview]
Message-ID: <1645632119.08819e2c0d3643729488b2236d191d27303e62af.tastytea@gentoo> (raw)
commit: 08819e2c0d3643729488b2236d191d27303e62af
Author: Yuan Liao <liaoyuan <AT> gmail <DOT> com>
AuthorDate: Wed Feb 23 15:18:01 2022 +0000
Commit: Ronny Gutbrod <gentoo <AT> tastytea <DOT> de>
CommitDate: Wed Feb 23 16:01:59 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=08819e2c
gnome-extra/extension-manager: Add comments about the package's tests
Signed-off-by: Yuan Liao <liaoyuan <AT> gmail.com>
.../extension-manager/extension-manager-9999.ebuild | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/gnome-extra/extension-manager/extension-manager-9999.ebuild b/gnome-extra/extension-manager/extension-manager-9999.ebuild
index 1bf8f484c..4a5dfc5e0 100644
--- a/gnome-extra/extension-manager/extension-manager-9999.ebuild
+++ b/gnome-extra/extension-manager/extension-manager-9999.ebuild
@@ -42,9 +42,24 @@ src_configure() {
meson_src_configure
}
-# disable AppStream test
+# Tests are skipped because as of version 0.2.3, the tests only validate
+# resource files and do not verify any functionality of the program. Those
+# validations are either already handled by QA checks or are not relevant on
+# Gentoo. For more information about the rationale, please refer to:
+# https://github.com/gentoo/guru/commit/f896bee213fbb62c70e818c1bf503fee2a41919a#comments
+#
+# If tests are to be executed in the future because the upstream adds
+# functionality tests in the future or for other reasons, and should there be
+# no convenient way to skip the validations, the following variable values need
+# to be set:
+#
+# IUSE="test"
+# # 'Validate appstream file' test case requires Internet connection
+# PROPERTIES="test_network"
+# RESTRICT="test"
+# BDEPEND="test? ( dev-libs/appstream-glib dev-util/desktop-file-utils )"
src_test() {
-:
+ :
}
pkg_postinst() {
next reply other threads:[~2022-02-24 11:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 11:10 Ronny Gutbrod [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-10 15:44 [gentoo-commits] repo/proj/guru:master commit in: gnome-extra/extension-manager/ Julien Roy
2025-01-10 15:44 Julien Roy
2025-01-10 15:44 Julien Roy
2024-04-29 21:27 David Roman
2024-04-27 12:09 Julien Roy
2023-12-11 6:50 Viorel Munteanu
2023-11-09 3:11 Haelwenn Monnier
2023-11-09 3:11 Haelwenn Monnier
2023-11-09 3:11 Haelwenn Monnier
2023-06-04 6:20 Viorel Munteanu
2023-06-04 6:20 Viorel Munteanu
2023-06-04 6:20 Viorel Munteanu
2023-05-06 6:59 Viorel Munteanu
2022-12-01 3:59 Haelwenn Monnier
2022-10-07 13:13 Arthur Zamarin
2022-10-07 13:13 Arthur Zamarin
2022-10-07 13:13 Arthur Zamarin
2022-09-17 11:49 Ronny Gutbrod
2022-08-02 10:55 Haelwenn Monnier
2022-04-23 17:49 Haelwenn Monnier
2022-03-29 0:22 Ronny Gutbrod
2022-03-25 11:24 Ronny Gutbrod
2022-03-25 11:24 Ronny Gutbrod
2022-03-25 11:24 Ronny Gutbrod
2022-02-24 11:10 Ronny Gutbrod
2022-02-24 11:10 Ronny Gutbrod
2022-02-24 11:10 Ronny Gutbrod
2022-02-23 0:33 Ronny Gutbrod
2022-02-23 0:33 Ronny Gutbrod
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=1645632119.08819e2c0d3643729488b2236d191d27303e62af.tastytea@gentoo \
--to=gentoo@tastytea.de \
--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