From: "Julien Roy" <julien@jroy.ca>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: gnome-extra/extension-manager/
Date: Fri, 10 Jan 2025 15:44:23 +0000 (UTC) [thread overview]
Message-ID: <1736458054.ee9215b6f28bad0321bdaf7fedd2dc8dde83a875.julien@gentoo> (raw)
commit: ee9215b6f28bad0321bdaf7fedd2dc8dde83a875
Author: Yuan Liao <liaoyuan <AT> gmail <DOT> com>
AuthorDate: Thu Jan 9 21:26:56 2025 +0000
Commit: Julien Roy <julien <AT> jroy <DOT> ca>
CommitDate: Thu Jan 9 21:27:34 2025 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=ee9215b6
gnome-extra/extension-manager: Add 0.6.0
Closes: https://bugs.gentoo.org/946487
Signed-off-by: Yuan Liao <liaoyuan <AT> gmail.com>
| 1 +
.../extension-manager-0.6.0.ebuild | 83 ++++++++++++++++++++++
2 files changed, 84 insertions(+)
--git a/gnome-extra/extension-manager/Manifest b/gnome-extra/extension-manager/Manifest
index 8dff7100f..30abd5416 100644
--- a/gnome-extra/extension-manager/Manifest
+++ b/gnome-extra/extension-manager/Manifest
@@ -1 +1,2 @@
DIST extension-manager-0.5.1.tar.gz 2248071 BLAKE2B 44fbd22961c462d1d3047e790e0054b77508476b927ae83b9677b7ad60df854287901c66a671c9c05d5a1f7857cf2f4dbad662604bed6322e8e02340880fa2d5 SHA512 7f5fc64adda0ea8c0d505c29d2a9037e565a42a66a2c151f5ed21267c715aa1738b94b075704fe4479961356a255c9aea450155b969a60cb78edf40ae448681f
+DIST extension-manager-0.6.0.tar.gz 2444382 BLAKE2B d45ad954ddcbd7853b90403d3947beadfda4d06f9dcd4ffabd570e625ff0365fe9df71109595c1f89dd199c283ee867314f0c7f21e095160e66b56229a782224 SHA512 cf2419c699534fae57539dc6cf86ff22afb925ba8dd7adc186e3d5c14b2cff474f487bfc16dbaac01de80c4811e73dcd0df80fe2b79db70fd409d0a56561b78a
diff --git a/gnome-extra/extension-manager/extension-manager-0.6.0.ebuild b/gnome-extra/extension-manager/extension-manager-0.6.0.ebuild
new file mode 100644
index 000000000..8c43bb5d5
--- /dev/null
+++ b/gnome-extra/extension-manager/extension-manager-0.6.0.ebuild
@@ -0,0 +1,83 @@
+# Copyright 2022-2025 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit gnome2-utils meson xdg
+
+if [[ ${PV} == *9999 ]]; then
+ inherit git-r3
+ EGIT_REPO_URI="https://github.com/mjakeman/extension-manager.git"
+else
+ SRC_URI="https://github.com/mjakeman/extension-manager/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+ KEYWORDS="~amd64"
+fi
+
+DESCRIPTION="A native tool for browsing, installing, and managing GNOME Shell Extensions"
+HOMEPAGE="https://mattjakeman.com/apps/extension-manager"
+
+LICENSE="GPL-3+"
+SLOT="0"
+
+BDEPEND="
+ dev-libs/glib:2
+ dev-util/blueprint-compiler
+ sys-devel/gettext
+ virtual/pkgconfig
+"
+
+RDEPEND="
+ dev-libs/glib:2
+ dev-libs/json-glib
+ dev-libs/libxml2
+ gui-libs/gtk:4[introspection]
+ >=gui-libs/libadwaita-1.6.0:1[introspection]
+ net-libs/libsoup:3.0
+"
+
+DEPEND="
+ ${RDEPEND}
+"
+
+src_configure() {
+ local emesonargs=(
+ -Dpackage="ebuild"
+ -Ddistributor="Gentoo GURU <guru-bugs@gentoo.org>"
+
+ # sys-libs/libbacktrace has been last-rited in ::gentoo
+ # and is thus unavailable
+ -Dbacktrace=false
+ )
+ if has live ${PROPERTIES}; then
+ # Produce a development build for live ebuild
+ emesonargs+=( -Ddevelopment=true )
+ fi
+ meson_src_configure
+}
+
+# Tests are skipped because as of version 0.3.0, 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 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 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"
+# RESTRICT="!test? ( test )"
+# BDEPEND="test? ( dev-libs/appstream-glib dev-util/desktop-file-utils )"
+src_test() {
+ :
+}
+
+pkg_postinst() {
+ xdg_pkg_postinst
+ gnome2_schemas_update
+}
+
+pkg_postrm() {
+ xdg_pkg_postrm
+ gnome2_schemas_update
+}
next reply other threads:[~2025-01-10 15:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 15:44 Julien Roy [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
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-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=1736458054.ee9215b6f28bad0321bdaf7fedd2dc8dde83a875.julien@gentoo \
--to=julien@jroy.ca \
--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