What to do with the kdebase/workspace dependency?

[Nicolas Alvarez]

Alexander Neundorf wrote:
> When kdebase/workspace is installed, it installs a Config.cmake file,
> which contains information about the installed package.
> This file assumes that processcore is always there, so it adds this
> imported target.
> I'd say either kdebase/workspace has to be installed completely, or we
> have to support installing it in parts.
> Or we don't use the Config.cmake files anymore, and again use logic to see
> what is actually existing on the system.
> The idea with the Config.cmake files is that the installing package knows
> exactly what will be there once it has been installed and puts that
> information into this file.
> Now if packagers afterwards split this into smaller parts, the the
> Config.cmake file becomes wrong.

Is there any reason why we can't just use find_library to get a path to 
libprocessui.so?

-- 
Nicolas

(I read mailing lists through Gmane. Please don't Cc me on replies; it makes 
me get one message on my newsreader and another on email.)