On Fri, Apr 21, 2006 at 12:20:17PM +0200, Bartosz Fabianowski wrote:
> Delivered-To: [EMAIL PROTECTED]
> Delivered-To: [EMAIL PROTECTED]
> Date: Fri, 21 Apr 2006 12:20:40 +0200
> From: Bartosz Fabianowski <[EMAIL PROTECTED]>
> User-Agent: Thunderbird 1.5 (X11/20060402)
> To: Mario Sergio Fujikawa Ferreira <[EMAIL PROTECTED]>
> CC: Michael Nottebrock <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: [kde-freebsd] kdenetwork3/kopete/kopete-devel and libjingle
> (google
> talk)
> In-Reply-To: <[EMAIL PROTECTED]>
>
> >Well, I see no harm on maintaining a development port which every
> >once in a while is copied over the stable port.
>
> For the time being, a development port won't be even possible. Once 0.12
> is released, Kopete development will shift to the KDE4 version, which
> cannot be packaged as a devel port because it depends on other
> unreleased software such as qt4-copy and kdelibs4.
I would like to know if I can commit the net/kdenetwork3 vs
net-im/kopete split.
I would be using the kopete from kdenetwork for the current
incarnation of net-im/kopete.
This would help us clean any rough edges (on the split side)
before the final kopete 0.12.
I have the 0.12 beta 2 kopete running like a charm here.
I've even added an option (make config) allowing one to build against
libjingle 0.3.0 instead of the one shipped with kopete. This is my
current installation mind you.
I am currently trying to reach kopete developers (bugs.kde.org)
to include 0.12 patches into the distribution.
Regards,
--
Mario S F Ferreira - DF - Brazil - "I guess this is a signature."
feature, n: a documented bug | bug, n: an undocumented feature
_______________________________________________
kde-freebsd mailing list
[email protected]
http://freebsd.kde.org/mailman/listinfo/kde-freebsd
