9 Oct
2023
9 Oct
'23
3:14 p.m.
Slávek Banko via tde-devels wrote:
On Monday 09 of October 2023 13:11:58 deloptes via
tde-devels wrote:
No problem Slavek,
I stumbled on this by accident because I started building for Debian 11.8.
I have also did not check if there are updates upstream. I'll have a look.
However the header QT_H did not change. I was expecting TQT_H to work. What
is your plan regarding this?
pinentry-tqt-1.2.1$ grep QT_H tqt/*
tqt/secqinternal_p.h:#ifndef QT_H
tqt/secqinternal_p.h:#endif // QT_H
tqt/secqlineedit.h:#ifndef QT_H
tqt/secqlineedit.h:#endif // QT_H
tqt/secqstring.h:#ifndef QT_H
tqt/secqstring.h:#endif // QT_H
BR
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Hi Michele, Slavek, all,
The recent changes QT_* -> TQT_* in headers (example Q_EXPORT ->
TQ_EXPORT) are impacting the pinentry application.
I remember we discussed once how we'll proceed with updates, but I do
not recall. I could prepare the patches and probably push upstream. What
is your view on this matter?
thanks in advance
BR
E.
Hi Emanoil,
this very good reminder and very accurate timing, because at the end of
the month is planned the final R14.1.1.
I completely forgot that the current changes will also have an impact on
pinentry-tqt. It will be great if you can prepare a patch and try to push
it into upstream. I assume that for R14.1.1, we can add a patch into
extra-dependencies repository, unless a new upstream version will be
available.
Thank you!
Cheers