Re: Plasma Next Beta 1
On Sat, May 10, 2014 at 08:24:30PM +0200, šumski wrote: Yeah. Thus also kfilemetadata (so this baloo tar is unbuildable - not just cause master branch is packaged instead of frameworks one ;-) And since the WIP kde-baseapps is here (somehow this would fit more with Applications releases than Plasma?), IMHO, one could possibly include Kate, Konsole and plasma-nm (with required libs) - though libs target to be part of KF5? kfilemetadata added 924a6450f7d37132d8cb7afc025cd58b4c4aa562e1ddee82976f14f60df861c6 milou added 33fec64b34a9f7bebffd422e3f221cf6461fc49355f5081cf04b5612d752325d baloo remade from frameworks branch daa5fcb94d18f54e082d09dd32131f161dcd7e3f99e0b54eaa7f9a280fb0940a kde-baseapps removed sysadmin ticket filed to update, files also at.. http://starsky.19inch.net/~jr/tmp/plasma-4.96.0/ Jonathan ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Next Beta 1
On Saturday 10 of May 2014 02:45:03 Michael Palimaka wrote: On 05/10/2014 02:07 AM, Jonathan Riddell wrote: Tars are available for Plasma Next Beta 1 Soon to be landing on depot.kde.org http://depot.kde.org unstable/plasma/4.96.0 Temporary site: http://starsky.19inch.net/~jr/tmp/plasma-4.96.0/ http://starsky.19inch.net/~jr/tmp/plasma-4.96.0/SHA256Sum This release works with Qt 5.2 although it is probably better with Qt 5.3 RC. It'll need KDE Frameworks 5 Beta 2 which was quietly released yesterday. It should not overlap with kde-runtime or kdelibs from kdelibs4 land but much of it will overlap with kde-workspace from kdelibs4 land, it's new versions. The translations will also overlap with translations from kde sc 4.13. One suggested solution it to install 4.13 translations into their own directory and patch kdelibs4 to read from that directory. I may well have made mistakes, this release is still quite undefined. If there are tars I should/should not have included, if there are branches I should have used, if there are version numbers I should have set differently either in the tars or internally let me know. The Plasma team is still discussing what it still be called so for now I'll call it Plasma Next. I hope to announce this on Tuesday but how knows. Good luck :) Jonathan ___ Kde-packager mailing list kde-packa...@kde.org https://mail.kde.org/mailman/listinfo/kde-packager . Also do we need a milou package? I think it's required by plasma-workspace (see lookandfeel/contents/runcommand/RunCommand.qml). Yeah. Thus also kfilemetadata (so this baloo tar is unbuildable - not just cause master branch is packaged instead of frameworks one ;-) And since the WIP kde-baseapps is here (somehow this would fit more with Applications releases than Plasma?), IMHO, one could possibly include Kate, Konsole and plasma-nm (with required libs) - though libs target to be part of KF5? Cheers, Hrvoje Moving forward, are there plans to split kde-baseapps or is that remaining unchanged? Best regards, Michael ___ Kde-packager mailing list kde-packa...@kde.org https://mail.kde.org/mailman/listinfo/kde-packager signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Plasma Next Beta 1
Tars are available for Plasma Next Beta 1 Soon to be landing on depot.kde.org unstable/plasma/4.96.0 Temporary site: http://starsky.19inch.net/~jr/tmp/plasma-4.96.0/ http://starsky.19inch.net/~jr/tmp/plasma-4.96.0/SHA256Sum This release works with Qt 5.2 although it is probably better with Qt 5.3 RC. It'll need KDE Frameworks 5 Beta 2 which was quietly released yesterday. It should not overlap with kde-runtime or kdelibs from kdelibs4 land but much of it will overlap with kde-workspace from kdelibs4 land, it's new versions. The translations will also overlap with translations from kde sc 4.13. One suggested solution it to install 4.13 translations into their own directory and patch kdelibs4 to read from that directory. I may well have made mistakes, this release is still quite undefined. If there are tars I should/should not have included, if there are branches I should have used, if there are version numbers I should have set differently either in the tars or internally let me know. The Plasma team is still discussing what it still be called so for now I'll call it Plasma Next. I hope to announce this on Tuesday but how knows. Good luck :) Jonathan ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma Next Beta 1
On 05/10/2014 02:07 AM, Jonathan Riddell wrote: Tars are available for Plasma Next Beta 1 Soon to be landing on depot.kde.org http://depot.kde.org unstable/plasma/4.96.0 Temporary site: http://starsky.19inch.net/~jr/tmp/plasma-4.96.0/ http://starsky.19inch.net/~jr/tmp/plasma-4.96.0/SHA256Sum This release works with Qt 5.2 although it is probably better with Qt 5.3 RC. It'll need KDE Frameworks 5 Beta 2 which was quietly released yesterday. It should not overlap with kde-runtime or kdelibs from kdelibs4 land but much of it will overlap with kde-workspace from kdelibs4 land, it's new versions. The translations will also overlap with translations from kde sc 4.13. One suggested solution it to install 4.13 translations into their own directory and patch kdelibs4 to read from that directory. I may well have made mistakes, this release is still quite undefined. If there are tars I should/should not have included, if there are branches I should have used, if there are version numbers I should have set differently either in the tars or internally let me know. The Plasma team is still discussing what it still be called so for now I'll call it Plasma Next. I hope to announce this on Tuesday but how knows. Good luck :) Jonathan ___ Kde-packager mailing list kde-packa...@kde.org https://mail.kde.org/mailman/listinfo/kde-packager Hi, Since powedevil and libkscreen are in extragear, is it expected to use the same versions as plasma stuff? It's not clear to me the full list of packages which fall under the Plasma Next umbrella. Also do we need a milou package? I think it's required by plasma-workspace (see lookandfeel/contents/runcommand/RunCommand.qml). Moving forward, are there plans to split kde-baseapps or is that remaining unchanged? Best regards, Michael ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
