Re: Bug#515663: ITP: kmess2 -- Windows(R) Live(R) Messenger(R) Client for KDE4.
Rafael Belmonte schreef:
Kmess 1.5 is the current stable version of kmess, and built in KDE3,
kmess2 is the current development version of kmess and built in KDE4, it
is not stable yet, but it provides functional svn snapshots regularly.
I am not sure if kmess and kmess2 packages should be at the same time in
the archive until kmess2 is not stable.
What do you think?
I've CC'd two of the KMess developers I know, Diederik and Valerio.
There's a pro and a con for adding KMess2 to the repositories:
- pro: KMess 1.5 is a very old and much less featured version of KMess.
- con: It's still even in alpha.
I'm not sure but I think I remember some very old packages being
replaced by newer versions, which were not declared stable. In any case,
I think it would be best to have a version of KMess 1.5 in the
repositories
(http://kmess.svn.sourceforge.net/svnroot/kmess/tags/kmess/kmess-1.5.2),
and the latest tag of KMess 2 (that's kmess-2.0alpha2).
If no maintainers can be found, I'll opt to be a maintainer for KMess,
it'd be a good learning path for me and I do have a little coding
experience with the program (I added a little feature, heh.)
If there's any Debian policy I missed on this, please let me know.
Sjors
Reply to: