Comment 5 for bug 1590599

I think we can plan to make a snap of the KDE framework stack which is
maintained by Ubuntu and can safely be used by other snaps. We don't yet
have the content-sharing interface, but as soon as we do, we can make a
kde-base snap which provides a full set of libraries that apps can just use.

Generally we avoid cross-vendor sharing of libraries, but in the case of
something fundamental like KDE it makes sense to trust the community
process to produce something of high quality that everyone can depend
on. Apps can individually choose how much of that they link to
dynamically, vs static linking or library bundling in their own snaps.

Mark

On 09/06/16 09:54, Scarlett Gately Clark wrote:
> I don't know how much it will help, but I am taking a different
> approach, and adding a misc part and adding all the build-packages for
> all the parts there so that apt will only be used for the misc, qt, and
> frameworks parts, rather than for every part. This will all be better
> when snaps can use libraries from other snaps as then I will build a
> snap for each framework and we only need to pull in the required pre-
> built frameworks snaps that are needed. When I tried to put each
> framework as a part it was a spectacular level of fail as the dependency
> chain was enormous.
>