Re: [opensuse-packaging] kdenetwork3-InstantMessaging vs kopete (fwd)
From: Pascal Bleser
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).
That's partly right - kde svn modules are all packaged as kmodulename3, then any subpackage splits are at the discretion of the SUSE KDE maintainers.
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 is an issue for every KDE application - kdepim3 contains kmail 1.9. It's only a problem in cases like this where the app team decides to do an out-of-kde-module release.
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.
I'd disagree about the trickery and incorrect package name charges. Its correct name according to convention is kdenetwork3-XXX. The problem here is of the Kopete dev team's making (which I belong to). Kopete has been tied to the KDE release cycle since KDE 3.2, it's only for this 0.12 release that we have broken this link. I'm looking for a solution that will allow us to upgrade from 3.5.x to kopete-0.12 to <future location of kopete> 4.0, 3.6, etc. I'll get back to you when I find it. Will Stephenson
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Will Stephenson wrote:
From: Pascal Bleser
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).
That's partly right - kde svn modules are all packaged as kmodulename3, then any subpackage splits are at the discretion of the SUSE KDE maintainers.
Ah, ok, wasn't aware of that detail.
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 is an issue for every KDE application - kdepim3 contains kmail 1.9. It's only a problem in cases like this where the app team decides to do an out-of-kde-module release.
Indeed. In this case, the behavior is inconsistent. If kopete wants to be included in the KDE release distribution, it should adhere to the KDE release cycles. Breaking out of it as in this case causes the package versioning issues as I described extensively. Well, ok, thinking about it again, there probably isn't anything we can do about the package name (kdenetwork3-InstantMessenger). Maybe add a "Provides: kopete = 0.12.0" tag in the kdenetwork3-InstantMessenger RPM ? That way, I could make a "kopete-0.12.1" package that would be seen as an upgrade to kdenetwork3-InstantMessenger (at least I think so, also depends on the package management frontend).
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 ? ... 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.
I'd disagree about the trickery and incorrect package name charges. Its correct name according to convention is kdenetwork3-XXX. The problem here is
Ok, admittedly, if kopete adheres to the KDE release cycles and if it's not a decision made by the packagers, you are absolutely right.
of the Kopete dev team's making (which I belong to). Kopete has been tied to the KDE release cycle since KDE 3.2, it's only for this 0.12 release that we have broken this link.
Ok, thanks for clarifying.
I'm looking for a solution that will allow us to upgrade from 3.5.x to kopete-0.12 to <future location of kopete> 4.0, 3.6, etc. I'll get back to you when I find it.
Will, thanks for your feedback and your time on this ;)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
participants (2)
-
Pascal Bleser -
Will Stephenson