<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/08/16 08:36, Christian Ehrhardt
wrote:<br>
</div>
<blockquote
cite="mid:CAATJJ0JytV5hAkJ+-Lz38p+n0CcXBhWR3WtpabnxnqmDEEEQBg@mail.gmail.com"
type="cite">
<div dir="ltr">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.
<div class="gmail_extra">Or turning around the statement: How a
snap would ensure things are picked up by the "host" in
classic.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">A generic solution for this isn't the
most important feature - as it might also break isolation more
than we like.</div>
<div class="gmail_extra">So - if considered as a generic feature
- this might just end up as one of the constraints for snaps
on classic.<br>
</div>
<div class="gmail_extra">But for a few common cases (like
manpages see bug 1575593 I think we should design and provide
something that can be commonly used).</div>
</div>
</blockquote>
<br>
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.<br>
<br>
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.<br>
<br>
Mark<br>
</body>
</html>