From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: USE flag: gui or X?
Date: Thu, 20 Feb 2025 22:11:49 -0000 (UTC) [thread overview]
Message-ID: <pan$ed1bb$6d5a408d$6b649496$d64b41df@cox.net> (raw)
In-Reply-To: 4102d3da-a1d6-04bd-2a37-d30209e536c1@gentoo.org
Andrey Grozin posted on Thu, 20 Feb 2025 13:15:46 +0000 (UTC) as
excerpted:
> I have a trivial question. I'm now working on the asymptote ebuild.
> asymptote has an optional gui - a separate python program xasy using
> pyqt5 and interacting with asy. From time immemorable, the USE flag
> controlling it was called X. Should I rename it to gui?
>
> Can a pyqt5 program (like xasy) run on wayland? I never used wayland,
> and have no idea (though I heard that qt programs can run on wayland).
> If xasy can run on wayland, then the USE flag name X is misleading, and
> should be replaced by gui.
So your question was answered (gui), but I'm looking at that pyqt5 and
thinking...
pyqt *5*? What's upstream's story on pyqt6 support? Kinda weird to have
a new major version still stuck on qt5. Is it even worth the time's-
ticking flag and dep or will it just need removed in a few months when the
last pyqt5 revdeps are cleaned up?
(Maybe upstream's working on it and this asymptote-3.0 release as
mentioned in the earlier thread is a temporary stop-gap until they've
finished stabilizing the qt6 version? In which case, probably worth
keeping the flag and dep for now to avoid the disruption. But then the
3.0 major version stuck on qt5 is even more weird.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2025-02-20 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 13:15 [gentoo-dev] USE flag: gui or X? Andrey Grozin
2025-02-20 13:28 ` Filip Kobierski
2025-02-20 13:46 ` Andrey Grozin
2025-02-20 22:11 ` Duncan [this message]
2025-02-21 4:56 ` [gentoo-dev] " Andrey Grozin
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='pan$ed1bb$6d5a408d$6b649496$d64b41df@cox.net' \
--to=1i5t5.duncan@cox.net \
--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