[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Coinstallability for kfilemetadata and baloo
From:       Bernd Steinhauser <bernd () bernd-steinhauser ! de>
Date:       2014-05-23 18:08:51
Message-ID: 537F8EB3.40607 () bernd-steinhauser ! de
[Download RAW message or body]

Hi,
On 21/05/14 13:47, Vishesh Handa wrote:
> On Monday, May 19, 2014 07:48:50 PM Bernd Steinhauser wrote:
>> However, I'm not sure what to do about baloo (btw, is there a
>> topic-specificlist?). Of course, we could just install it to a different
>> prefix, but we'd like to avoid that. So before making bigger changes to
>> baloo, I'd like to ask if there are plans to make this coinstallable with
>> the KDE4-based version?It's not listed in [1-2].
>>
> Split Baloo up based on the directory stuff -
>
> src/core - Library - Coinstallable
> src/file/lib/ - Libraries that can be coinstalled
> src/file/ - Binaries - Qt5 ones replace the Qt4 ones
> src/kioslaves - Co-installable
> src/runner - Coinstallable
> src/tools - binaries. Qt5 ones can replace the Qt4 ones
> src/xapian - Library - co-installable
> src/pim - Not compiled in KF5, it will be split out.
>
>
Yes, most of the stuff is coinstallable, but the binaries are not. Especially 
cases like src/file are things we would like to avoid. From a developer side, it 
is easy to say that the new binaries replace the old ones, but from our side, 
it's hard to handle.
We would like to keep the packages close to upstream tarballs (which in this 
case is baloo). Splitting is possible, although for a source distro like ours it 
is a bit harder than for binary distros, but it can be done. However, the past 
told us, that we should try to avoid it.
Anyway, I take it you don't want to make the binaries coinstallable. But the 
bigger issue I see is actually the cmake files.
If both kde4-based and kf5-based baloo are installed, they share (by default) 
/usr/lib/cmake/Baloo, which is where cmake looks for the installed version of 
baloo and therefore the package that owns these will get the packages to link to it.
Maybe here a rename (i.e. cmake/KF5Baloo or something like that) would be good 
to ensure that both versions can be used when trying to compile programs against 
them?

In fact, this problem persists for other packages as well, that's why I renamed 
the installed cmake files for kfilemetadata as well.

Best Regards,
Bernd

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]