public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/kde:master commit in: media-sound/elisa/
Date: Wed,  5 Jul 2017 22:56:11 +0000 (UTC)	[thread overview]
Message-ID: <1499294942.a646c02f09011655d49cea08eae4aadbe27c68e2.asturm@gentoo> (raw)

commit:     a646c02f09011655d49cea08eae4aadbe27c68e2
Author:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Wed Jul  5 22:49:02 2017 +0000
Commit:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Wed Jul  5 22:49:02 2017 +0000
URL:        https://gitweb.gentoo.org/proj/kde.git/commit/?id=a646c02f

media-sound/elisa: Add missing RDEPENDs

Upstream commit e565837e7fc928e48d60924438a82552a7187e42

Reported-by: holgersson in #gentoo-kde

Package-Manager: Portage-2.3.6, Repoman-2.3.1

 media-sound/elisa/elisa-9999.ebuild | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/media-sound/elisa/elisa-9999.ebuild b/media-sound/elisa/elisa-9999.ebuild
index 4f8ad7cba8..b6c8400c62 100644
--- a/media-sound/elisa/elisa-9999.ebuild
+++ b/media-sound/elisa/elisa-9999.ebuild
@@ -16,7 +16,7 @@ IUSE=""
 # TODO:
 # - Bogus deps
 # - optional features
-RDEPEND="
+COMMON_DEPEND="
 	$(add_frameworks_dep baloo)
 	$(add_frameworks_dep kconfig)
 	$(add_frameworks_dep kconfigwidgets)
@@ -33,8 +33,12 @@ RDEPEND="
 	$(add_qt_dep qtsql)
 	$(add_qt_dep qtwidgets)
 "
-DEPEND="${RDEPEND}
+DEPEND="${COMMON_DEPEND}
 	sys-devel/gettext
 "
+RDEPEND="${COMMON_DEPEND}
+	$(add_qt_dep qtgraphicaleffects)
+	$(add_qt_dep qtquickcontrols)
+"
 
 RESTRICT+=" test"


             reply	other threads:[~2017-07-05 22:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 22:56 Andreas Sturmlechner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-10 15:04 [gentoo-commits] proj/kde:master commit in: media-sound/elisa/ Andreas Sturmlechner
2024-07-01 17:03 Andreas Sturmlechner
2024-03-08 20:17 Andreas Sturmlechner
2024-02-27 22:28 Sam James
2024-02-25 20:02 Sam James
2023-12-23 15:46 Andreas Sturmlechner
2022-11-12 10:17 Andreas Sturmlechner
2020-09-29 12:51 Andreas Sturmlechner
2020-06-09 18:14 Andreas Sturmlechner
2020-05-27 21:23 Andreas Sturmlechner
2020-05-20 19:28 Andreas Sturmlechner
2020-05-09 19:59 Andreas Sturmlechner
2020-04-29 16:10 Andreas Sturmlechner
2020-04-24 10:47 Andreas Sturmlechner
2020-03-30  0:32 Andreas Sturmlechner
2020-02-04  1:16 Andreas Sturmlechner
2019-12-07 11:43 Andreas Sturmlechner
2019-11-30  9:42 Andreas Sturmlechner
2019-11-10 23:13 Andreas Sturmlechner
2019-11-10 23:13 Andreas Sturmlechner
2019-07-15 16:00 Andreas Sturmlechner
2019-06-05 16:12 Andreas Sturmlechner
2018-07-11 20:35 Johannes Huber
2018-06-11 18:58 Johannes Huber
2018-04-14 16:21 Johannes Huber
2018-04-14 16:08 Johannes Huber
2018-04-08 14:01 Johannes Huber
2018-04-08 13:26 Johannes Huber
2018-04-08 13:26 Johannes Huber
2017-12-10 21:53 Andreas Sturmlechner
2017-07-21 17:54 Andreas Sturmlechner
2017-04-06 19:59 Johannes Huber
2017-04-06 19:59 Johannes Huber
2017-03-01 23:42 Andreas Sturmlechner
2017-02-26 15:31 Johannes Huber

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=1499294942.a646c02f09011655d49cea08eae4aadbe27c68e2.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