Yes exactly, once an application has been released based on Qt5/KF5 it shouldn't be coinstallable with the same application that is Qt4/kdelibs4 based. Most (and eventually all) kf5 based applications include a settings/config migrator that migrates settings from kdelibs4 locations to kf5 locations if the new location doesn't have any settings. Also both kdelibs4 based and kf5 based binaries, shared data files etc would conflict if both were installed at once.
On Wed, Jan 13, 2016 at 10:38 AM, René J.V. <[email protected]> wrote: > On Thursday January 14 2016 00:54:59 [email protected] wrote: > >>It is not clear to me at this point what aim you have. Are you aiming for >>full install (including applications) in parallel, or for non-conflicting >>core packages so that different applications from both KDE4 and KF5 could be >>installed ? > > I'm defining that aim as I go, basically. I'm trying to allow co-installation > of the core packages; the framework and whatever of "plasma" I'll be able to > port. As Jeremy pointed out, that is largely possible and intended because a > gradual transition has been foreseen so that KDE4 applications can function > normally "under" KF5. > As to applications: I'm not convinced that there would be much interest in > having the KDE4 and KF5 version of all applications installed. For some, like > KDevelop this can be justified for now, but for others it is probably good > enough to be able to have either the KDE4 or the KF5 version activated at any > given time. And then there is KDE PIM which shouldn't even be allowed to > co-exist: it appears that one cannot go back (without risk) after having run > the KF5 version. > Concurrent installation of the 2 "flavours" makes sense mostly if each of the > 2 flavours has advantages that the other doesn't have. > >>Which means that independently of binary compatibility, all KDE4 Portfiles >>would have to be revbumped if the change is applied. > > Yes... > >>It seems to me that the best way to get feedback would be to commit some of >>the changes, if indeed these are harmless. On the other hand, as I am under >>the impression that it is getting possible to have KF5 somewhat working >>within Macports (did not try myself), I also think that most useful thing for >>the users base at this point would be to include KF5 to Macports’ provided >>ports. > > Marko is trying out a number of KF5 ports now. It would be nice if someone > else could check the changes I've been making to KDE4 ports for side-effects > that I have missed. > > Cheers, > René > _______________________________________________ > [email protected] > List Information: https://mail.kde.org/mailman/listinfo/kde-mac > KDE/Mac Information: http://community.kde.org/Mac _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
