<div dir="ltr">On 9 January 2018 at 09:01, Alexander Kanavin <span dir="ltr"><<a href="mailto:alexander.kanavin@linux.intel.com" target="_blank">alexander.kanavin@linux.intel.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 01/08/2018 06:00 PM, Ross Burton wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-RRECOMMENDS_avahi-dev = "expat-dev libcap-dev libdaemon-dev dbus-dev glib-2.0-dev update-rc.d-dev"<br>
-RRECOMMENDS_avahi-dev_append_<wbr>libc-glibc = " gettext-dev"<br>
-<br>
-RRECOMMENDS_avahi-dev[nodeprr<wbr>ecs] = "1"<br>
-<br>
</blockquote>
<br></span>
Cool, I was wondering about the necessity of this stuff.<br>
<br>
Thanks for cleaning up, we can also perhaps look into splitting gettext-native recipe into a sane set of parts, and use them in a carefully targeted way, rather than the current -minimal-native approach, which is hackish.<br></blockquote><div><br></div><div>ross/gettext is slowly heading in that direction.</div><div><br></div><div>Ross </div></div></div></div>