Hello! On Wednesday 07 June 2006 18:31, Matt Rogers wrote: > On Wednesday 07 June 2006 18:13, Olivier Goffart wrote: > > I also think we will probably meet the requirement to go in KDE 3.5.x > > Kopete 0.12 will be well tested since it has been released. > > And it will be merged with trunk. > > > > But do we want Kopete 0.12.x in KDE 3.5.x ? > > no
Why not? Kopete is already included in KDE 3.5, but old, outdated one. There is no even proper encoding support in Oscar protocol in that version! This outdated version has lots of bugs which are already fixed in 0.12, generating lots of bug reports. Imagine regular user of Linux distribution which uses KDE. This user starts Kopete, finds it unworkable, sends bug report. What do you guys reply to this bug report? "Upgrade to 0.12", right? How this poor person is supposed to upgrade? Download tarball, compile and install? C'mon, it's XXI century. Do you really think that average Linux user is sophisticated enough to do this? Even if he's sophisticated to compile and install, this will replace files which belong to kdenetwork package, creating inconsistency in package management system. This inconsistency is a time bomb, actually: another software update will rewrite Kopete 0.12 with the version from kdenetwork package again. Which other ways to install Kopete 0.12 are available? RPM or DPKG package? It won't work, because this package will conflict with files from kdenetwork. Install into home directody and use KDEDIRS path? I use this method, but it won't work for most users, because it requires even more sophistication than compiling and installing. What I want to tell you is that this old Kopete included in kdenetwork is the real pain in the ass, both for users and developers. It makes the new Kopete painful to install for users. Also, it makes life more complicated for developers, because de facto there are 3 different Kopete branches: trunk, 0.12 and the one in kdenetwork. The only resolution of the problem I've outlined above is to eliminate old kdenetwork version of Kopete as soon as possible. There are only two ways to do it: either completely remove Kopete from kdenetwork package, or replace it with Kopete 0.12. Which way do you prefer? -- Oleg Girko, http://www.infoserver.ru/~ol/ _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
