How to snap packages that provide "extra" files to be used by something else

[Mark Shuttleworth]

On 12/08/16 08:36, Christian Ehrhardt wrote:
> In the context of the request I was thinking more about snaps on
> classic and how e.g. a "classic" system could pick up those.
> Or turning around the statement: How a snap would ensure things are
> picked up by the "host" in classic.
>
> A generic solution for this isn't the most important feature - as it
> might also break isolation more than we like.
> So - if considered as a generic feature - this might just end up as
> one of the constraints for snaps on classic.
> But for a few common cases (like manpages see bug 1575593 I think we
> should design and provide something that can be commonly used).

If the CUPS in the classic environment is a snap, then the snap-to-snap
interface will work for classic just as well as all-snap Ubuntu Core.

If the CUPS is a deb, then something (could be snapd) would need to know
how to handle the interface in enough detail to feed the bits to CUPS.

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20160812/bbc9829c/attachment.html>