19 Aug
2017
19 Aug
'17
11:26 p.m.
Hi
I am not sure if someone is interested but I played with pinentry recently
and produced a working executable from pinentry-0.8.3 (qt3 code ported to
tqt) and a base of pinentry-0.9.7.
I just can't do the packaging myself so that I may replace the existing
pinentry-* with the one I modified, so that it satisfies all dependencies.
I can provide the binary if someone wants to use it for now, but the
question here is wouldn't it be better to get the code into the official
pinentry project?
and why is kleopatra-trinity* kmail-trinity* kmailcvt-trinity*
kontact-trinity* tde-trinity* tdepim-trinity*
dependant on pinentry-qt/qt4 ?
Is it because pinentry-qt was previously qt3, but now qt5?
It pulls in qt5 libraries which I want to avoid.
regards
21 Aug
21 Aug
11:29 p.m.
New subject: [trinity-devel] pinentry-tqt
On Sunday 20 of August 2017 01:26:18 deloptes wrote:
Hi
I am not sure if someone is interested but I played with pinentry
recently and produced a working executable from pinentry-0.8.3 (qt3
code ported to tqt) and a base of pinentry-0.9.7.
I just can't do the packaging myself so that I may replace the existing
pinentry-* with the one I modified, so that it satisfies all
dependencies.
I can provide the binary if someone wants to use it for now, but the
question here is wouldn't it be better to get the code into the
official pinentry project?
and why is kleopatra-trinity* kmail-trinity* kmailcvt-trinity*
kontact-trinity* tde-trinity* tdepim-trinity*
dependant on pinentry-qt/qt4 ?
Is it because pinentry-qt was previously qt3, but now qt5?
It pulls in qt5 libraries which I want to avoid.
regards
That sounds very good! I had started preparing the same thing a long time
ago, but due to lack of time I did not move forward. I was considering to
prepare a separate git repository and package that could be kept along
with upstream. I'm not sure what's the chance to push the code directly
into the upstream.
Yes, Debian package pinentry-qt was previously for Qt3, whereas this
package is now for Qt5 :(
Cheers
--
Slávek
22 Aug
22 Aug
5:27 a.m.
Slávek Banko wrote:
That sounds very good! I had started preparing the
same thing a long time
ago, but due to lack of time I did not move forward. I was considering to
prepare a separate git repository and package that could be kept along
with upstream. I'm not sure what's the chance to push the code directly
into the upstream.
Yes, Debian package pinentry-qt was previously for Qt3, whereas this
package is now for Qt5
do you want me to upload it to a bug ticket?
We'll be on vacation leaving tomorrow evening. I may answer when back
regards
5:38 a.m.
Slávek Banko wrote:
That sounds very good! I had started preparing the
same thing a long time
ago, but due to lack of time I did not move forward. I was considering to
prepare a separate git repository and package that could be kept along
with upstream. I'm not sure what's the chance to push the code directly
into the upstream.
Yes, Debian package pinentry-qt was previously for Qt3, whereas this
package is now for Qt5
do you want me to upload it to a bug ticket?
We'll be on vacation leaving tomorrow evening. I may answer when back
regards
2649
days inactive
2652
days old
3 comments
2 participants
participants (2)
-
deloptes -
Slávek Banko