<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 22 December 2015 at 17:13, Karstens, Nate <span dir="ltr"><<a href="mailto:Nate.Karstens@garmin.com" target="_blank">Nate.Karstens@garmin.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Based on this I can see two approaches: 1) locate all DHCP client recipes in the same layer because they all provide the same functionality or 2) include alternatives
in other layers (which in this case really just means dhcpcd as the ISC DHCP client and busybox shouldn’t really be considered “alternatives”).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">In either case it probably makes sense to remove the old recipe from meta-alt-desktop-extras.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> </span></p></blockquote></div><br>Definitely (2), oe-core needs *something* to provide DHCP functionality but meta-networking is the obvious fit for an alternative choice.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>