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 w
On Fri, Jul 4, 2014 at 11:13 AM, 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.
>
Just to clarify. All the libraries and plugins are co-instalable. It's just
the e
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 "pla
On 4 July 2014 10:13, Vishesh Handa wrote:
> On Fri, Jul 4, 2014 at 10:59 AM, Jonathan Riddell 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
On 4 July 2014 10:13, Vishesh Handa wrote:
> On Fri, Jul 4, 2014 at 10:59 AM, Jonathan Riddell 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
On Fri, Jul 4, 2014 at 10:59 AM, Jonathan Riddell 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
> wrote:
> >
> > d58af08286e9d85ea6afa77831692c02efba9ba8ddebf57fd342854062425d39
> > A kfilemetadata5-4.98
On Fri, Jul 04, 2014 at 12:54:22AM +0200, Vishesh Handa wrote:
>On Thu, Jul 3, 2014 at 11:05 PM, Jonathan Riddell
> wrote:
>
> d58af08286e9d85ea6afa77831692c02efba9ba8ddebf57fd342854062425d39
> A kfilemetadata5-4.98.0.tar.xz
> 24f401be4beda474a386bd223390477ece9ab3329183d0f69b
