<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">El 21/09/16 a las 08:18, Gustavo
Niemeyer escribió:<br>
</div>
<blockquote
cite="mid:CANySw1=Hb4xRKxxsEeC3VuhsfSwZgnWww0v7TfhN+cyvC_Rayg@mail.gmail.com"
type="cite">
<div dir="ltr">That was a good explanation indeed, thanks John.
<div><br>
</div>
<div>Can we do something better than just recommend it on
classic? The feature is common enough that this should be a
requirement, I think.</div>
</div>
</blockquote>
<br>
Even though Recommends doesn't sound like a fit, this is its use:<br>
<br>
<dl>
<dd>
<p>
This declares a strong, but not absolute, dependency.
</p>
<p>
The <samp>Recommends</samp> field should list packages that
would be found
together with this one in all but unusual installations.[1]</p>
</dd>
</dl>
Suggests would be the wrong dependency declaration though:<br>
<br>
<blockquote>This is used to declare that one package may be more
useful with one or more
others. Using this field tells the packaging system and the user
that the
listed packages are related to this one and can perhaps enhance
its usefulness,
but that installing this one without them is perfectly
reasonable.[1]<br>
</blockquote>
<blockquote
cite="mid:CANySw1=Hb4xRKxxsEeC3VuhsfSwZgnWww0v7TfhN+cyvC_Rayg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div><br>
</div>
<div>The problem then is how to drop the package when building
the Ubuntu Core image.</div>
</div>
</div>
</blockquote>
<br>
If things are still the same, images are built with --no-recommends.<br>
<br>
Cheers<br>
Sergio<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://www.debian.org/doc/debian-policy/ch-relationships.html">https://www.debian.org/doc/debian-policy/ch-relationships.html</a><br>
<br>
</body>
</html>