From: "Davide Pesavento" <pesa@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtplugininfo/
Date: Sun, 24 Apr 2016 19:25:30 +0000 (UTC) [thread overview]
Message-ID: <1461525893.d3dd39bc6bd833a9946385fa5ee0884ab7bdd1e2.pesa@gentoo> (raw)
commit: d3dd39bc6bd833a9946385fa5ee0884ab7bdd1e2
Author: Davide Pesavento <pesa <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 24 19:24:53 2016 +0000
Commit: Davide Pesavento <pesa <AT> gentoo <DOT> org>
CommitDate: Sun Apr 24 19:24:53 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d3dd39bc
dev-qt/qtplugininfo: new package
Package-Manager: portage-2.2.28
dev-qt/qtplugininfo/Manifest | 1 +
dev-qt/qtplugininfo/metadata.xml | 17 +++++++++++++++++
dev-qt/qtplugininfo/qtplugininfo-5.6.0.ebuild | 24 ++++++++++++++++++++++++
3 files changed, 42 insertions(+)
diff --git a/dev-qt/qtplugininfo/Manifest b/dev-qt/qtplugininfo/Manifest
new file mode 100644
index 0000000..28138b9
--- /dev/null
+++ b/dev-qt/qtplugininfo/Manifest
@@ -0,0 +1 @@
+DIST qttools-opensource-src-5.6.0.tar.xz 9817788 SHA256 0d244c61bbe5505cb94310e980b06ef13dd573511e80ccbdc060f71d5462219d SHA512 d1bee83715d336bc0257b114bbfc7f97cf11f7d5ad75b45376c9b4a55224fa74b82fdc4c6db60dd0917553eef76b0286dde1d3b46e0262ef17c9a3dbbc142400 WHIRLPOOL 96d7fadd39575bf30c23684311aa59c7c86d6e65f49992a71151dcc330840336ad0508a602783c475b55f7f4d5a60c38ffbf380cb91f0974e1a1b352d59e4c2a
diff --git a/dev-qt/qtplugininfo/metadata.xml b/dev-qt/qtplugininfo/metadata.xml
new file mode 100644
index 0000000..08d85fc
--- /dev/null
+++ b/dev-qt/qtplugininfo/metadata.xml
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="project">
+ <email>qt@gentoo.org</email>
+ <name>Gentoo Qt Project</name>
+ </maintainer>
+ <upstream>
+ <bugs-to>https://bugreports.qt.io/</bugs-to>
+ <doc>http://doc.qt.io/</doc>
+ </upstream>
+ <slots>
+ <subslots>
+ Must only be used by packages that are known to use private parts of the Qt API.
+ </subslots>
+ </slots>
+</pkgmetadata>
diff --git a/dev-qt/qtplugininfo/qtplugininfo-5.6.0.ebuild b/dev-qt/qtplugininfo/qtplugininfo-5.6.0.ebuild
new file mode 100644
index 0000000..edc1fd1
--- /dev/null
+++ b/dev-qt/qtplugininfo/qtplugininfo-5.6.0.ebuild
@@ -0,0 +1,24 @@
+# Copyright 1999-2016 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=6
+QT5_MODULE="qttools"
+inherit qt5-build
+
+DESCRIPTION="Qt5 plugin metadata dumper"
+
+if [[ ${QT5_BUILD_TYPE} == release ]]; then
+ KEYWORDS="~amd64 ~x86"
+fi
+
+IUSE=""
+
+DEPEND="
+ ~dev-qt/qtcore-${PV}
+"
+RDEPEND="${DEPEND}"
+
+QT5_TARGET_SUBDIRS=(
+ src/qtplugininfo
+)
next reply other threads:[~2016-04-24 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 19:25 Davide Pesavento [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-25 14:36 [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtplugininfo/ Andreas Sturmlechner
2021-09-08 16:55 Andreas Sturmlechner
2021-10-16 8:20 Andreas Sturmlechner
2022-04-17 19:29 Sam James
2022-06-18 17:25 Andreas Sturmlechner
2023-01-08 21:45 Andreas Sturmlechner
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=1461525893.d3dd39bc6bd833a9946385fa5ee0884ab7bdd1e2.pesa@gentoo \
--to=pesa@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