Am Montag, 26. Januar 2015, 22:11:40 schrieb Albert Astals Cid:

> El Dilluns, 26 de gener de 2015, a les 11:13:57, Jeremy Whiting va escriure:

> > Eike,

> >

> > Thanks for looking into this and notifying us also. I heard some vague

> > reports but nothing concrete like this.

> >

> > On Mon, Jan 26, 2015 at 8:58 AM, Eike Hein <hein@kde.org> wrote:

> > > Hi,

> > >

> > > it's becoming increasingly clear from feedback that we didn't

> > > think the decision to ship KF5 apps in 14.12 through very well.

> > >

> > > Distros are currently rolling it out as an upgrade to KDE 4

> > > systems over the last 4.x apps, and users are running into the

> > > following problems:

> > >

> > > * KF5-based apps don't pick up visual settings from KDE 4 and

> > >

> > > can't be configured because System Settings 5 is usually not

> > > co-installable.

> > >

> > > I believe this needs to be addressed in the QPA plugin we

> > > ship with Frameworks and have added a new BKO product for

> > > the plugin as well as opened a ticket:

> > >

> > > https://bugs.kde.org/show_bug.cgi?id=343336

> > >

> > > * Some apps apparently don't use the support class to migrate

> > >

> > > the app config file to the fd.o location, which means from

> > > the user POV they lose all settings for the app.

> >

> > I know kns3 isn't using this support class to migrate it's registry of

> > what's been installed to the new locations it uses. Just curious, what

> > "support class" are you referring to here?

> > I know kanagram/khangman also don't use this, but that's probably not as

> > important, since they don't have many settings anyway.

>

> Kdelibs4ConfigMigrator see

> http://quickgit.kde.org/?p=kgeography.git&a=blob&h=12b104f1f99ebd3cc55933df26229c2f47111a9d&hb=9f6c8f4bb518ea8e1ecc4b9dd56bead796426d03&f=src%2Fmain.cpp

> for an example on how to use it.

Is there also somewhere an example for Kdelibs4Migration, to migrate application data from $KDEHOME/share/apps?

> Cheers,

> Albert

>

> >

> > > Here we need to go through every app and check and fix it,

> > > and make sure we don't ship anything without that QA check

> > > again on future ports.

> > >

> > > I cross-posted this to k-c-d and r-t for visibility - I suggest

> > > we discuss the Frameworks side on k-c-d and the release QA side

> > > on r-t.

> > >

> > >

> > > Cheers,

> > > Eike

> > > _______________________________________________

> > > release-team mailing list

> > > release-team@kde.org

> > > https://mail.kde.org/mailman/listinfo/release-team

>

> _______________________________________________

> release-team mailing list

> release-team@kde.org

> https://mail.kde.org/mailman/listinfo/release-team