From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/PyQt6/
Date: Wed, 3 Aug 2022 16:05:15 +0000 (UTC) [thread overview]
Message-ID: <1659542684.b8eb4195cc67263847739bb589b0ad494106c76b.ionen@gentoo> (raw)
commit: b8eb4195cc67263847739bb589b0ad494106c76b
Author: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 3 16:02:29 2022 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Wed Aug 3 16:04:44 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b8eb4195
dev-python/PyQt6: add bugref for qmake6 path
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
dev-python/PyQt6/PyQt6-6.3.1.ebuild | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/dev-python/PyQt6/PyQt6-6.3.1.ebuild b/dev-python/PyQt6/PyQt6-6.3.1.ebuild
index f943118bccb3..ba0245d7b232 100644
--- a/dev-python/PyQt6/PyQt6-6.3.1.ebuild
+++ b/dev-python/PyQt6/PyQt6-6.3.1.ebuild
@@ -84,8 +84,7 @@ src_configure() {
echo ${*/#/${state}}
}
- # hack: currently lacking qt6_get_bindir (or alternatively have
- # qmake6 in PATH like qmake5 is so it wouldn't matter)
+ # workaround until bug 863395 has something to offer
local qmake6=$(qt5_get_bindir)/qmake6
qmake6=${qmake6//qt5/qt6}
next reply other threads:[~2022-08-03 16:05 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 16:05 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-17 2:22 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyqt6/ Ionen Wolkens
2025-02-07 3:29 Ionen Wolkens
2024-12-16 8:42 Ionen Wolkens
2024-12-12 22:36 Ionen Wolkens
2024-12-06 5:10 Ionen Wolkens
2024-11-25 7:46 Ionen Wolkens
2024-11-25 7:46 Ionen Wolkens
2024-11-22 20:00 [gentoo-commits] repo/gentoo:master commit in: dev-python/PyQt6/ Michał Górny
2024-11-13 10:04 Ionen Wolkens
2024-09-20 11:01 Arthur Zamarin
2024-09-18 6:36 Arthur Zamarin
2024-09-12 13:45 Sam James
2024-09-05 1:23 Sam James
2024-09-03 12:31 Ionen Wolkens
2024-09-02 6:16 Sam James
2024-08-31 2:42 Ionen Wolkens
2024-08-12 18:21 Arthur Zamarin
2024-08-08 10:05 Sam James
2024-07-24 9:03 Ionen Wolkens
2024-07-19 14:39 Ionen Wolkens
2024-06-29 12:29 Jakov Smolić
2024-06-28 18:05 Sam James
2024-06-28 18:05 Sam James
2024-06-28 14:45 Ionen Wolkens
2024-05-13 0:46 Sam James
2024-04-27 10:11 Ionen Wolkens
2024-04-26 11:31 Ionen Wolkens
2023-12-25 15:49 Ionen Wolkens
2023-12-22 22:40 Mart Raudsepp
2023-12-19 20:58 Ionen Wolkens
2023-12-17 18:29 Arthur Zamarin
2023-12-16 12:06 Ionen Wolkens
2023-12-04 16:08 Ionen Wolkens
2023-11-15 17:20 Arthur Zamarin
2023-11-05 15:49 Ionen Wolkens
2023-11-05 13:52 Ionen Wolkens
2023-10-30 14:47 Ionen Wolkens
2023-10-18 13:03 Ionen Wolkens
2023-10-14 14:48 Ionen Wolkens
2023-09-28 13:07 Ionen Wolkens
2023-09-28 13:07 Ionen Wolkens
2023-09-28 13:07 Ionen Wolkens
2023-09-15 6:08 Ionen Wolkens
2023-09-05 13:05 Ionen Wolkens
2023-09-05 13:05 Ionen Wolkens
2023-08-06 4:32 Ionen Wolkens
2023-07-25 0:10 Ionen Wolkens
2023-06-17 4:49 Ionen Wolkens
2023-06-17 4:49 Ionen Wolkens
2023-06-13 13:20 Ionen Wolkens
2023-06-03 5:21 Ionen Wolkens
2023-05-11 17:01 Ionen Wolkens
2023-04-23 1:21 Ionen Wolkens
2023-04-22 8:04 Ionen Wolkens
2023-04-22 6:53 Ionen Wolkens
2023-04-22 6:53 Ionen Wolkens
2023-04-19 20:07 Ionen Wolkens
2023-04-19 20:07 Ionen Wolkens
2023-04-16 9:02 Ionen Wolkens
2023-02-13 15:59 Ionen Wolkens
2023-02-13 11:46 Ionen Wolkens
2023-02-06 17:45 Ionen Wolkens
2023-01-30 19:11 Ionen Wolkens
2023-01-28 15:56 Ionen Wolkens
2022-10-28 20:53 Ionen Wolkens
2022-10-28 20:47 Ionen Wolkens
2022-10-20 13:34 Ionen Wolkens
2022-10-04 1:33 Ionen Wolkens
2022-08-03 18:58 Ionen Wolkens
2022-08-03 13:51 Ionen Wolkens
2022-08-03 0:22 Ionen Wolkens
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=1659542684.b8eb4195cc67263847739bb589b0ad494106c76b.ionen@gentoo \
--to=ionen@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