Am Dienstag, 5. Mai 2015, 11:30:45 schrieb Raymond Wooninck:
My proposal would be that if there are people ready to take the KDE4 maintenance task, then please let us know and I will copy the whole KDE:Current project to a new project named KDE:KDE4 and grant full access to this project to those new maintainers. This would be a very good starting point, given that actually everything is inside that project.
Probably not a bad idea, at least for while. (I don't really see much point in keeping KDE4 "forever" like it's being done with KDE3. Plasma5 is not really something completely different like KDE4's Plasma was...) I would definitely help out here. Regarding keeping it in Tumbleweed or even making it co-installable, I don't really think we should aim for that. It's not just the package and executable names that conflict, but also things like DBUS interfaces and PolKit actions (in particular for KAuth helpers). Also the Qt4/Qt5 clashes come to mind here. E.g. a kdenlive4 would just crash on startup with the Qt5-based libmlt shipped in Tumbleweed. I have also e.g. seen Plasma5 taking up 100% of CPU when I started to maintain my repo because powerdevil5 tried to use the KDE4 KAuth backlighthelper (to get the necessary privileges for backlight control) which crashed and was restarted over and over again. All of that is definitely possible to workaround, but will be a lot of work and be quite hackish too I suppose (and I know what I'm talking of... ;) ). Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org