Hi,

tested on i386.

On Sun, Jul 20, 2008 at 09:56:24PM +0200, viq wrote:
> Here is my attempt at bringing net/psi more up-to-date. I know release
> candidates are not usually considered for inclusion, and the port
> probably needs a bit polishing, but I wanted to get it out into the open
> for people to look at and comment.
> 
> A couple comments:
> - it needs qca2, which doesn't coexist well at build time with qca1 (and
> vice versa), thus any newer version can't be included in bulk builds
> untill this is solved

I didn't had that problems, as I don't have qca1 installed.

> - you need to install qca-ossl (port attached), a qca2 plugin for SSL
> support for psi to talk over SSL/TLS with the server

Built and installed without problems. My jabber server uses a selfsigned
certificate, qca2-ossl complained about it, clicking on "Continue" let
me have an encrypted connection to it.

> - you need to install qca-gnupg (port attached), a qca2 plugin for GnuPG
> support if you want to use GnuPG encryption for your conversations

Built and installed without problems, too.
Assigned a key to somebody and had an encryted chat with him.

> - I didn't manage to convince those plugins to have a library version
> - the desktop file is there, put Psi in my xfce menu, but it doesn't
> have an icon, I didn't look into that yet
> - patches/patch-src_psioptions_cpp added for Psi to compile with
> something as old as GCC 3.3.5, given to me from someone involved with
> psi as an "ugly hack" that works, but is not nearly nice enough to
> be included upstream
> 
> 
> Lightly tested on i386, seems to work for me.

So as far as I can see, everything works as expected.
Played around with config a bit, chatted, encrypted and unencrypted.

The only thing I see in the terminal from where I started Psi is:

Object::connect: No such slot QCA::DirWatch::watcher_changed(QString)
qca-gnupg: patching DirWatch to fix failed connect

I don't know if this is anything important...

But besides that, everything seems to work fine and it looks great :-)
--
simon

Reply via email to