Mailinglist Archive: opensuse-packaging (89 mails)

[Pascal Bleser <pascal.bleser@xxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Schiele wrote:
> On Sun, Dec 18, 2005 at 10:21:34PM +0100, Pascal Bleser wrote:
>> - - 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
> 
> And why can't you communicate this to end users?

Please point me to the all-suse-users mailing list ;)

>> 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
> 
> Huh?  Kopete is part of the official KDE release.  If you wanted to change
> this this would result in renaming almost all KDE packages to the names of
> their individual applications and listing _all_ the individual version numbers
> of the single applications in the KDE spec files.

Not exactly. Kopete is part of the official KDE release in the sense that when KDE is released, it
includes the latest stable version of kopete.
But kopete has a versioning scheme of its own, follows its own releases, _independently_ of KDE
releases.

e.g. now kopete 0.12.0 is going to be released, but not KDE 3.5.1 at the same time

In the mean time, I'd like to package kopete 0.12.0 for KDE 3.4.2 (SUSE 10.0) and below, if
possible. That's my point in this mail.

cheers
- --
  -o) Pascal Bleser     http://linux01.gwdg.de/~pbleser/
  /\\ <pascal.bleser@xxxxxxxxx>       <guru@xxxxxxxxxxx>
 _\_v The more things change, the more they stay insane.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDpd2zr3NMWliFcXcRAmF/AJ0dwNpRD47ec84d9jxoNhzP6gaRHQCeNwUf
Xv+N9WgiNKI986AcnmJP0D8=
=+GhO
-----END PGP SIGNATURE-----