[packagekit] [PATCH] Allow the Plasma version to be specified for PK_PROVIDES_ENUM_PLASMA_SERVICE.

[Matthias Klumpp]

Looks good to me - if Richard doesn't complain about it, the patch can
go in, I think.
IMHO the string should be named "plasma4", because the "4" clearly
indicates the version of KDE frameworks. By using the Plasma version,
this would only lead to more confusion. 8I would even vote for giving
Plasma the same version number as the rest of KDE SC, because it is
probably the most important part of the desktop and it is what makes
KDE KDE.) Maybe ask the Plasma devs what solution they would prefer?
Cheers,
   Matthias

2011/11/18 Kevin Kofler <kevin.kofler at chello.at>:
> I wrote:
>> In order to support both KDE Plasma Workspaces 4 (libplasma 1) and the
>> upcoming KDE Plasma Workspaces 5 (libplasma 2), we need to also accept
>> query strings of the plasma5(dataengine-weather) format, not just the
>> dataengine- weather format implicitly assumed to be plasma4.
>
> FWIW, I hope my namespace versioning is going to make sense in the long run.
> When I started using plasma4, it "obviously" made sense: Plasma Workspaces
> was versioned 4.x, libplasma was versioned libplasma.so.4. But now there is
> a big confusion about what version numbers are being used: the new libplasma
> is codenamed "libplasma2", there are even people arguing for calling the new
> KDE Frameworks "KDE Frameworks 1" rather than 5, etc. :-( (Hopefully at
> least Plasma Workspaces 5 will remain version 5.) And plasma-desktop's
> versioning was always its own, in KDE SC 4.6.5, it claims to be version 0.4.
> I hope this isn't going to become as confusing as Debian's "kdelibs5" for
> kdelibs 4.x.
>
>        Kevin Kofler
>
> _______________________________________________
> PackageKit mailing list
> PackageKit at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/packagekit
>