On Saturday 14 October 2006 12:43, Rafael Espíndola wrote: > Currently kopete, psi and tapioca have a private copy of libjingle. > The one in tapioca is build as an independent package. The ones in > kopete and psi are build with the rest of the software. > > What do you think about changing kopete and psi to use an external > libjingle provided by the tapioca project? The code is available at > > https://svn.sourceforge.net/svnroot/tapioca-voip/libjingle/trunk > > A possible work list for doing this: > *) update the libjingle in kopete > *) update the libjingle in psi > *) move any bug fixes present in kopete or psi "upstream" > *) remove the copies from kopete and psi > > The reason I suggest using tapioca's version is because it is build as > a shared library and include pkg-config support. Another advantage is > that I work with some tapioca developers, so it should be easier to > get a svn account in it then to create a new project just for hosting > libjingle. > > Best Regards, > Rafael
And how is it kept up to date with the one on www.sf.net/projects/libjingle? -- Matt _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
