On Thu, 20 Feb 2025, Duncan wrote:
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?
I see no
Andrey Grozin posted on Thu, 20 Feb 2025 13:15:46 + (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
> controlli
On Thursday, February 20th, 2025 at 14:15, Andrey Grozin
wrote:
> Hello *,
>
> 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 control
On Thu, 20 Feb 2025, Filip Kobierski wrote:
PyQt are Python bindings for the Qt GUI toolkit.
That means that the question you're asking is "Should a QT app
have USE=gui or USE=X for enabling the graphical user interface?".
In that case I think the answer is obvious: it should be USE=gui.
Thanks.
Hello *,
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 (l
