FS#2277 - psi incorrectly packaged

Attached to Project: Arch Linux
Opened by Mircea Bardac (IceRAM) - Thursday, 24 February 2005, 11:00 GMT
Last edited by Dale Blount (dale) - Thursday, 24 February 2005, 14:06 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To dorphell (dorphell)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Psi 0.9.2 package had it's criptographic dependencies built with it, because nobody needed them.

Psi 0.9.3 depends on QCA (QT Cryptography Architecture), because QCA will also be used by KDE in the future.

QCA has some plugings: QCA-SASL & QCA-TLS.

In order for Psi to have SSL support when connecting to Jabber servers, QCA-TLS is used. Psi can live without QCA-TLS, but not without QCA.

Yesterday, Psi 0.9.3 was packed. I had a look over the PKGBUILD and I've noticed that QCA-TLS is built within. QCA-TLS is more part of QCA than Psi (I may say). Some other program might need QCA-TLS also.

Note also that QCA-TLS is delivered in a separate archive, and I personally don't know how it could compile with the old PKBUILD which considers it a part of Psi's archive (I might have missed something in that archive, but I don't think so).


http://bbs.archlinux.org/viewtopic.php?t=7517#49807 (main developer's comments)
http://mircea.bardac.net/psi/
This task depends upon

Closed by  dorphell (dorphell)
Thursday, 24 February 2005, 16:45 GMT
Reason for closing:  Not a bug
Additional comments about closing:  no bug.
Comment by dorphell (dorphell) - Thursday, 24 February 2005, 16:43 GMT
There's third-party qca-tls in psi. Whatever libs are included in the psi package are all part of psi and if it includes its own version of qca-tls, so be it. Right now no other package needs this package so I'm not changing it. When KDE starts depending on it, when the package is added, I'll make psi use it.

No bug here, closing.

Loading...