public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-editors/qxmledit/
Date: Fri, 23 Feb 2024 11:20:55 +0000 (UTC)	[thread overview]
Message-ID: <1708687249.79afacaddbb1a11ef2bbdd47f79760a5bed89639.arthurzam@gentoo> (raw)

commit:     79afacaddbb1a11ef2bbdd47f79760a5bed89639
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 23 11:20:14 2024 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Fri Feb 23 11:20:49 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=79afacad

app-editors/qxmledit: fix dependencies on Qt imageformats

Closes: https://bugs.gentoo.org/925300
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 .../qxmledit/{qxmledit-0.9.18.ebuild => qxmledit-0.9.18-r1.ebuild}     | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/app-editors/qxmledit/qxmledit-0.9.18.ebuild b/app-editors/qxmledit/qxmledit-0.9.18-r1.ebuild
similarity index 96%
rename from app-editors/qxmledit/qxmledit-0.9.18.ebuild
rename to app-editors/qxmledit/qxmledit-0.9.18-r1.ebuild
index 7cb89f9e07c6..991f54019207 100644
--- a/app-editors/qxmledit/qxmledit-0.9.18.ebuild
+++ b/app-editors/qxmledit/qxmledit-0.9.18-r1.ebuild
@@ -16,7 +16,8 @@ KEYWORDS="~amd64 ~riscv ~x86"
 DEPEND="
 	dev-qt/qtconcurrent:5
 	dev-qt/qtcore:5
-	dev-qt/qtgui:5
+	dev-qt/qtgui:5[jpeg]
+	dev-qt/qtimageformats:5[mng]
 	dev-qt/qtnetwork:5
 	dev-qt/qtopengl:5
 	dev-qt/qtprintsupport:5


             reply	other threads:[~2024-02-23 11:20 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 11:20 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-05 19:54 [gentoo-commits] repo/gentoo:master commit in: app-editors/qxmledit/ Petr Vaněk
2024-06-06 17:28 Arthur Zamarin
2024-06-06 16:58 Arthur Zamarin
2024-02-23 11:49 Arthur Zamarin
2024-02-22 20:16 Arthur Zamarin
2019-08-12  6:16 Andreas Sturmlechner
2019-08-11 21:30 Thomas Deutschmann
2019-08-08  7:43 Agostino Sarubbo
2019-03-07 13:13 Michael Palimaka
2019-03-07 13:13 Michael Palimaka
2019-03-07 13:13 Michael Palimaka
2018-06-30  1:52 Michael Palimaka
2018-01-25 14:06 Michael Palimaka
2017-12-22  9:57 Michael Palimaka
2017-09-30  7:22 Michael Palimaka
2017-09-11 12:17 Michael Palimaka
2017-09-11 12:17 Michael Palimaka
2017-09-11 12:17 Michael Palimaka
2017-09-11 12:17 Michael Palimaka
2017-09-11 12:17 Michael Palimaka
2017-09-11 12:17 Michael Palimaka
2017-06-18 11:04 Michael Palimaka
2017-03-04  7:09 Michael Palimaka
2017-01-26 14:55 Michael Palimaka
2017-01-26 14:53 Agostino Sarubbo
2017-01-26 14:45 Agostino Sarubbo
2016-11-12 13:38 Michael Palimaka
2016-08-11 14:38 Michael Palimaka
2016-08-11 14:38 Michael Palimaka
2016-06-09 11:50 Michael Palimaka
2016-06-08 15:54 Michael Palimaka
2016-06-08 15:54 Michael Palimaka
2016-06-07 23:45 Davide Pesavento
2016-06-06 16:15 Agostino Sarubbo
2016-05-30 16:04 Davide Pesavento
2016-05-30 16:04 Davide Pesavento
2016-04-02 19:02 Davide Pesavento
2016-02-27  3:10 Davide Pesavento
2015-12-15 17:55 Michael Palimaka
2015-09-01 18:38 Tobias Klausmann

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=1708687249.79afacaddbb1a11ef2bbdd47f79760a5bed89639.arthurzam@gentoo \
    --to=arthurzam@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