From: "Yuan Liao" <liaoyuan@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: gnome-extra/extension-manager/
Date: Sun, 27 Mar 2022 20:39:45 +0000 (UTC) [thread overview]
Message-ID: <1648411838.fcb1069fe15e913d9449fdde723135f1e74e9d08.liaoyuan@gentoo> (raw)
commit: fcb1069fe15e913d9449fdde723135f1e74e9d08
Author: Yuan Liao <liaoyuan <AT> gmail <DOT> com>
AuthorDate: Sun Mar 27 20:10:18 2022 +0000
Commit: Yuan Liao <liaoyuan <AT> gmail <DOT> com>
CommitDate: Sun Mar 27 20:10:38 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=fcb1069f
gnome-extra/extension-manager: Add 0.3.0
Signed-off-by: Yuan Liao <liaoyuan <AT> gmail.com>
| 1 +
.../extension-manager-0.3.0.ebuild | 77 ++++++++++++++++++++++
2 files changed, 78 insertions(+)
--git a/gnome-extra/extension-manager/Manifest b/gnome-extra/extension-manager/Manifest
index bfb1562de..142564b18 100644
--- a/gnome-extra/extension-manager/Manifest
+++ b/gnome-extra/extension-manager/Manifest
@@ -1 +1,2 @@
DIST extension-manager-0.2.3.tar.gz 1384925 BLAKE2B 3bd98f67f419c646a4a7b9d1dee656de305eff5e35124f3765d5d9c82aff7d9e7bbeea912f24c0766c95e0c497b070831ee9922747f200bbcd57470a6adcec7e SHA512 9bb078f3d00cdfe1e84a757f7cce32f5a33333fdf4f60f3952523ac48779becab9c00da78974551f224c194806217eddf3116a29eb33f1e9982ff8caa5e06218
+DIST extension-manager-0.3.0.tar.gz 1431028 BLAKE2B 059d46118b57f204b1258a5d9c55587407130db3048b87be13294e6f426b5d8515475e6b7622cca3ed5951c3f2ed238d22a09ab4f4d1bf78196618b8fe580f29 SHA512 34642d81be67978ac039a17e0762fa1f44ea41720d066a5aeb7fa1e35f2f6ac25a7924b5daf3073ddf4caa3013e1e70b24c5df4c998920ebe1c8e0a875dbec0c
diff --git a/gnome-extra/extension-manager/extension-manager-0.3.0.ebuild b/gnome-extra/extension-manager/extension-manager-0.3.0.ebuild
new file mode 100644
index 000000000..7949012b7
--- /dev/null
+++ b/gnome-extra/extension-manager/extension-manager-0.3.0.ebuild
@@ -0,0 +1,77 @@
+# Copyright 2022 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 and installing GNOME Shell Extensions"
+HOMEPAGE="https://github.com/mjakeman/extension-manager"
+
+LICENSE="GPL-3+"
+SLOT="0"
+
+BDEPEND="
+ dev-libs/glib:2
+ dev-util/blueprint-compiler
+ virtual/pkgconfig
+"
+
+RDEPEND="
+ dev-libs/glib:2
+ dev-libs/json-glib
+ gui-libs/gtk:4[introspection]
+ gui-libs/libadwaita:1[introspection]
+ gui-libs/text-engine
+ net-libs/libsoup:3.0
+"
+
+DEPEND="
+ ${RDEPEND}
+"
+
+src_configure() {
+ local emesonargs=()
+ 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.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 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"
+# # '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() {
+ xdg_pkg_postinst
+ gnome2_schemas_update
+}
+
+pkg_postrm() {
+ xdg_pkg_postrm
+ gnome2_schemas_update
+}
next reply other threads:[~2022-03-27 20:39 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 20:39 Yuan Liao [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-31 13:34 [gentoo-commits] repo/proj/guru:dev commit in: gnome-extra/extension-manager/ Yuan Liao
2025-05-31 13:34 Yuan Liao
2025-01-10 14:36 Yuan Liao
2025-01-09 21:31 Yuan Liao
2025-01-09 21:31 Yuan Liao
2024-04-29 18:23 Yuan Liao
2024-04-27 11:42 Yuan Liao
2024-03-20 13:49 Yuan Liao
2023-12-08 21:09 Yuan Liao
2023-11-08 23:40 Yuan Liao
2023-11-08 23:31 Yuan Liao
2023-11-08 23:31 Yuan Liao
2023-07-06 14:57 Yuan Liao
2023-06-19 14:44 Yuan Liao
2023-06-19 14:44 Yuan Liao
2023-06-03 18:01 Yuan Liao
2023-06-03 18:01 Yuan Liao
2023-06-03 5:27 Yuan Liao
2023-05-05 19:42 Yuan Liao
2023-03-01 22:08 Yuan Liao
2022-12-12 1:37 Yuan Liao
2022-11-29 22:12 Yuan Liao
2022-10-06 15:54 Yuan Liao
2022-10-06 15:54 Yuan Liao
2022-10-06 15:54 Yuan Liao
2022-09-16 17:16 Yuan Liao
2022-08-30 13:27 Yuan Liao
2022-08-02 0:27 Yuan Liao
2022-06-04 17:57 Yuan Liao
2022-04-22 18:58 Yuan Liao
2022-03-21 5:25 Yuan Liao
2022-03-21 5:25 Yuan Liao
2022-03-21 5:25 Yuan Liao
2022-02-23 16:02 Yuan Liao
2022-02-23 14:12 Anna Vyalkova
2022-02-23 13:44 Anna Vyalkova
2022-02-23 13:44 Anna Vyalkova
2022-02-21 12:04 Yuan Liao
2022-02-21 12:04 Yuan Liao
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=1648411838.fcb1069fe15e913d9449fdde723135f1e74e9d08.liaoyuan@gentoo \
--to=liaoyuan@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