From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: kde-plasma/discover/
Date: Mon, 25 Feb 2019 17:05:37 +0000 (UTC) [thread overview]
Message-ID: <1551114326.b9d2de76f5f18741960420e2bad07ea3f064d35c.asturm@gentoo> (raw)
commit: b9d2de76f5f18741960420e2bad07ea3f064d35c
Author: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 25 17:01:33 2019 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Mon Feb 25 17:05:26 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b9d2de76
kde-plasma/discover: New package
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>
kde-plasma/discover/Manifest | 1 +
kde-plasma/discover/discover-5.15.1.ebuild | 58 ++++++++++++++++++++++++++++++
kde-plasma/discover/metadata.xml | 11 ++++++
3 files changed, 70 insertions(+)
diff --git a/kde-plasma/discover/Manifest b/kde-plasma/discover/Manifest
new file mode 100644
index 00000000000..42bf239a99e
--- /dev/null
+++ b/kde-plasma/discover/Manifest
@@ -0,0 +1 @@
+DIST discover-5.15.1.tar.xz 10441384 BLAKE2B 04b869dffded41a52faa856ded1d7b49f85f2fe9faaf92d95d0fc5f6657660daade6cde7f64bcfedb0c174b65834ba057a8a88639c45349c831baf1f28a57d57 SHA512 e3d998e1cd3f754bdf93ead71fd4fc848f495fa48bcce9489c105c0d7a5e25adefa2cc123e975a75ee71975816ead2a7f1e29a8bfbf31a320eb328183a954b41
diff --git a/kde-plasma/discover/discover-5.15.1.ebuild b/kde-plasma/discover/discover-5.15.1.ebuild
new file mode 100644
index 00000000000..fe7845f02cc
--- /dev/null
+++ b/kde-plasma/discover/discover-5.15.1.ebuild
@@ -0,0 +1,58 @@
+# Copyright 1999-2019 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+KDE_TEST="forceoptional"
+inherit kde5
+
+DESCRIPTION="KDE Plasma resources management GUI"
+HOMEPAGE="https://userbase.kde.org/Discover"
+KEYWORDS="~amd64 ~x86"
+IUSE="firmware"
+
+DEPEND="
+ $(add_frameworks_dep attica)
+ $(add_frameworks_dep kconfig)
+ $(add_frameworks_dep kconfigwidgets)
+ $(add_frameworks_dep kcoreaddons)
+ $(add_frameworks_dep kcrash)
+ $(add_frameworks_dep kdbusaddons)
+ $(add_frameworks_dep ki18n)
+ $(add_frameworks_dep kio)
+ $(add_frameworks_dep kirigami)
+ $(add_frameworks_dep kitemmodels)
+ $(add_frameworks_dep knewstuff)
+ $(add_frameworks_dep knotifications)
+ $(add_frameworks_dep kwidgetsaddons)
+ $(add_frameworks_dep kxmlgui)
+ $(add_qt_dep qtconcurrent)
+ $(add_qt_dep qtdbus)
+ $(add_qt_dep qtdeclarative)
+ $(add_qt_dep qtgui)
+ $(add_qt_dep qtnetwork)
+ $(add_qt_dep qtwidgets)
+ $(add_qt_dep qtxml)
+ firmware? ( sys-apps/fwupd )
+"
+RDEPEND="${DEPEND}
+ $(add_frameworks_dep kirigami)
+"
+
+src_prepare() {
+ kde5_src_prepare
+ # we don't need it with PackageKitBackend off
+ punt_bogus_dep KF5 Archive
+}
+
+src_configure() {
+ local mycmakeargs=(
+ -DCMAKE_DISABLE_FIND_PACKAGE_packagekitqt5=ON
+ -DCMAKE_DISABLE_FIND_PACKAGE_AppStreamQt=ON
+ -DCMAKE_DISABLE_FIND_PACKAGE_Snapd=ON
+ -DBUILD_FlatpakBackend=OFF
+ -DBUILD_FwupdBackend=$(usex firmware)
+ )
+
+ kde5_src_configure
+}
diff --git a/kde-plasma/discover/metadata.xml b/kde-plasma/discover/metadata.xml
new file mode 100644
index 00000000000..59d0ace33b0
--- /dev/null
+++ b/kde-plasma/discover/metadata.xml
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="project">
+ <email>kde@gentoo.org</email>
+ <name>Gentoo KDE Project</name>
+ </maintainer>
+ <use>
+ <flag name="firmware">Enable support for firmware upgrades using <pkg>sys-apps/fwupd</pkg></flag>
+ </use>
+</pkgmetadata>
next reply other threads:[~2019-02-25 17:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 17:05 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-28 14:32 [gentoo-commits] repo/gentoo:master commit in: kde-plasma/discover/ Mikle Kolyada
2019-03-01 10:05 Andreas Sturmlechner
2019-03-02 13:58 Andreas Sturmlechner
2019-03-02 13:58 Andreas Sturmlechner
2019-03-10 22:46 Andreas Sturmlechner
2019-05-18 17:24 Andreas Sturmlechner
2019-05-21 20:32 Andreas Sturmlechner
2020-04-23 22:07 Andreas Sturmlechner
2020-10-28 16:23 Sam James
2020-10-29 18:24 Georgy Yakovlev
2020-11-13 0:32 Thomas Deutschmann
2020-11-18 21:09 Andreas Sturmlechner
2021-04-04 16:03 Thomas Deutschmann
2021-04-06 19:47 Sam James
2021-04-06 19:51 Sam James
2021-04-06 20:08 Andreas Sturmlechner
2021-05-07 22:14 Andreas Sturmlechner
2021-06-10 18:05 Georgy Yakovlev
2021-11-13 17:28 Andreas Sturmlechner
2021-11-30 14:33 Andreas Sturmlechner
2022-03-08 17:18 Andreas Sturmlechner
2022-08-07 15:51 Andreas Sturmlechner
2022-09-25 18:50 Andreas Sturmlechner
2022-10-06 9:07 Andreas Sturmlechner
2022-11-16 8:55 WANG Xuerui
2023-05-10 7:51 Andreas Sturmlechner
2023-05-10 7:51 Andreas Sturmlechner
2023-09-30 10:00 Andreas Sturmlechner
2024-01-16 8:40 Andreas Sturmlechner
2024-01-30 20:26 Andreas Sturmlechner
2024-02-17 20:14 Andreas Sturmlechner
2024-02-17 20:14 Andreas Sturmlechner
2024-02-25 6:08 Andrew Ammerlaan
2024-03-05 17:22 Arthur Zamarin
2024-03-06 19:19 Arthur Zamarin
2024-04-26 10:38 Andrew Ammerlaan
2024-04-28 13:16 Andrew Ammerlaan
2024-09-21 8:29 Andreas Sturmlechner
2025-01-10 9:54 WANG Xuerui
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=1551114326.b9d2de76f5f18741960420e2bad07ea3f064d35c.asturm@gentoo \
--to=asturm@gentoo.org \
--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