Re: [kde-packager] Re: [kde-packager] Plasma 5 RC
On Fri, Jul 04, 2014 at 12:54:22AM +0200, Vishesh Handa wrote: On Thu, Jul 3, 2014 at 11:05 PM, Jonathan Riddell j...@jriddell.org wrote: d58af08286e9d85ea6afa77831692c02efba9ba8ddebf57fd342854062425d39 A kfilemetadata5-4.98.0.tar.xz 24f401be4beda474a386bd223390477ece9ab3329183d0f69b06ccb5859ecbba A baloo5-4.98.0.tar.xz Why do some tarballs have 5 appended to them? baloo5, kfilemetadata5, and milou5? Others seem to be missing the 5. Please either add the 5 everywhere or remove it from those 3. I renamed baloo's tar to baloo5 because it contains some libraries which most distros will want to co-install so I'd expect baloo (kdelibs4) and baloo (kf5) to exist in distro archives together, for which they need different names. kfilemetadata is similar. milou is probably a mistake, that won't co-exist. Would distros prefer upstream to rename the kf5 tars, or is it ok to tell distros to rename the older kdelibs4 versions? Jonathan ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [kde-packager] Re: [kde-packager] Plasma 5 RC
On Fri, Jul 4, 2014 at 10:59 AM, Jonathan Riddell j...@jriddell.org wrote: On Fri, Jul 04, 2014 at 12:54:22AM +0200, Vishesh Handa wrote: On Thu, Jul 3, 2014 at 11:05 PM, Jonathan Riddell j...@jriddell.org wrote: d58af08286e9d85ea6afa77831692c02efba9ba8ddebf57fd342854062425d39 A kfilemetadata5-4.98.0.tar.xz 24f401be4beda474a386bd223390477ece9ab3329183d0f69b06ccb5859ecbba A baloo5-4.98.0.tar.xz Why do some tarballs have 5 appended to them? baloo5, kfilemetadata5, and milou5? Others seem to be missing the 5. Please either add the 5 everywhere or remove it from those 3. I renamed baloo's tar to baloo5 because it contains some libraries which most distros will want to co-install so I'd expect baloo (kdelibs4) and baloo (kf5) to exist in distro archives together, for which they need different names. kfilemetadata is similar. milou is probably a mistake, that won't co-exist. A similar case exists for kactivites. It existed in kde4 as well and the current framework has the same name. I would really like the tarballs to have the same name. Also, baloo4 and 5 are not really co-installable. They both ship executables with the same name. -- Vishesh Handa ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [kde-packager] Re: [kde-packager] Plasma 5 RC
On 4 July 2014 10:13, Vishesh Handa m...@vhanda.in wrote: On Fri, Jul 4, 2014 at 10:59 AM, Jonathan Riddell j...@jriddell.org wrote: I renamed baloo's tar to baloo5 because it contains some libraries which most distros will want to co-install so I'd expect baloo (kdelibs4) and baloo (kf5) to exist in distro archives together, for which they need different names. kfilemetadata is similar. milou is probably a mistake, that won't co-exist. A similar case exists for kactivites. It existed in kde4 as well and the current framework has the same name. I would really like the tarballs to have the same name. Also, baloo4 and 5 are not really co-installable. They both ship executables with the same name. Co-installabilty of Plasma 4 and Plasma 5 with minimal work required by the distros is a must if we want to avoid the mess of KDE4. Already openSUSE has announced that you can't have both installed at once, which will force people to choose one or other, when what we really want is for them to be able to try Plasma 5 out while still being able to switch back to 4 if there are things that break their workflow. John. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [kde-packager] Re: [kde-packager] Plasma 5 RC
On 4 July 2014 10:13, Vishesh Handa m...@vhanda.in wrote: On Fri, Jul 4, 2014 at 10:59 AM, Jonathan Riddell j...@jriddell.org wrote: I renamed baloo's tar to baloo5 because it contains some libraries which most distros will want to co-install so I'd expect baloo (kdelibs4) and baloo (kf5) to exist in distro archives together, for which they need different names. kfilemetadata is similar. milou is probably a mistake, that won't co-exist. A similar case exists for kactivites. It existed in kde4 as well and the current framework has the same name. I would really like the tarballs to have the same name. Also, baloo4 and 5 are not really co-installable. They both ship executables with the same name. Co-installabilty of Plasma 4 and Plasma 5 with minimal work required by the distros is a must if we want to avoid the mess of KDE4. Already openSUSE has announced that you can't have both installed at once, which will force people to choose one or other, when what we really want is for them to be able to try Plasma 5 out while still being able to switch back to 4 if there are things that break their workflow. John. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [kde-packager] Re: [kde-packager] Plasma 5 RC
In data venerdì 4 luglio 2014 10:35:11, John Layt ha scritto: Hello John, really want is for them to be able to try Plasma 5 out while still being able to switch back to 4 if there are things that break their workflow. At least for openSUSE we have this planned. By choosing either the plasma5- session or the kdebase4-session packages, the user willl be able to install Plasma 5 or the 4.x workspace, making this switch easy enough (each switch willl remove / install the required packages). There are also other alternatives that can leverage the pacakge manager's capabilities (patterns, etc). Either way, packaging tools that allow this are available, and it's likely the same for other distros. I don't see this as a big issue as long as it's properly documented. It's *much, much better* than shipping stuff out of prefix. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 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
Re: [kde-packager] Re: [kde-packager] Plasma 5 RC
On Fri, Jul 4, 2014 at 11:13 AM, Vishesh Handa m...@vhanda.in wrote: I would really like the tarballs to have the same name. Also, baloo4 and 5 are not really co-installable. They both ship executables with the same name. Just to clarify. All the libraries and plugins are co-instalable. It's just the executables (baloo_file, baloostatus, balooctl, balooshow) that are not. Baloo in Plasma 5 does not ship with the PIM stuff. It probably never will. That will eventually be shipped somewhere else. -- Vishesh Handa ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [kde-packager] Re: [kde-packager] Plasma 5 RC
On Friday 04 July 2014 11:13:19 Vishesh Handa wrote: I would really like the tarballs to have the same name. Also, baloo4 and 5 are not really co-installable. They both ship executables with the same name. Are you saying that one can't use a kdepim with baloo support in a plasma workspace with baloo support until kdepim is ported to the 5 world ? /Sune ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
