KDE/Plasma 6.5.0 upgrade experiences

[Hefee]

Hey,

> Can some kind of meta package be created for all plasma packages?
> That way if any dependent package can't migrate yet, it will hold old
> others too.
> 
> Or that's not a proper solution?

* Nope a meta package does not solve this issue, there are meta-packages 
already and they are not solving this issue unfortunately.

Well we experiment a lot with different approaches to tight the packages 
together but haven't found a solution that is working an suitable until now. 
The problem is that we need to exclude different version of packages, that have 
no direct linkage. see plasma-desktop and plasma-workspace do not depend on 
each other.

* We used breaks and replaces in Plasma 4 times, but updating the long list of 
packages is very error prune, so we stop using that approach. 

* Normally one would use virtual packages like plasma-abi-6.5 and all packages 
would depend on that, that would solve this issue. But this virtual package 
would need a real packages that provides this virtual package. But there is 
not this "central package" for plasma that would be natural to ship this 
virtual package. Okay when writing this I'm thinking, well why not create a 
dummy plasma package without any content that simply provides the virtual 
package without any file content. Did we already tried this one?

* We use this virtual package approach for KDE PIM and that solved those 
mixing issues.

Regards,

hefee


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20251101/681961c2/attachment.sig>