-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi yall
I'd like to discuss the fact that the kopete package is called "kdenetwork3-InstantMessaging".
After doing some research (and with some help), I know that the decision to name that package this
way comes from SUSE (and not from the KDE team).
I think it's not a good idea to name kopete that way, although the name isn't the issue, but the
version number. In fact, it's e.g. kdenetwork3-InstantMessaging-3.5.0, but in reality it's some
kopete version (e.g. 0.11.x)
This raises a number of issues, where the most important is: now there's going to be a kopete 0.12.0
very soon... how are we supposed to name/number the package ?
- - we can't name it kdenetwork3-InstantMessaging-3.5.1, because when KDE 3.5.1 will be released
(possibly with a different kopete version but, most importantly, built against another version of
kdelibs3) it will collide
- - we can't name it kopete either (with a Conflicts:kdenetwork3-InstantMessaging) because end users
won't see that as an upgrade of kdenetwork3-InstantMessaging
- - we /could/ use the release to provide an upgrade, but that's
a) misusing the release tag for what is actually a different version number
b) a pain to maintain, because maybe SUSE releases an update kdenetwork3-InstantMessaging (with
kopete 0.11.x) and then we'd have to re-package it with a higher release number than SUSE
c) just an evil workaround and trickery whereas the issue should be solved by giving the package
its correct name in the first place
Could someone from SUSE please provide some feedback on this ? Stephan ? AJ ?
Would it be possible to rename kdenetwork3-InstantMessaging-3.5.0 to kopete-0.11.x ?
To me, it really doesn't make any sense to call it "kdenetwork3-InstantMessaging", kopete is not
even tightly bound to a specific KDE release, it just creates issues for community packagers who
want to provide packages of the latest kopete version.
thanks
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\