Thanks, Ross. There are currently two DHCP clients included in oe-core. The ISC DHCP client is in the dhcp recipe and udhcpc is included in busybox. There is also a very outdated recipe for dhcpcd in meta-alt-desktop-extras.

 

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”).

 

In either case it probably makes sense to remove the old recipe from meta-alt-desktop-extras.

 

Thoughts?

 

Nate

 

From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Tuesday, December 22, 2015 11:04 AM
To: Karstens, Nate <Nate.Karstens@garmin.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] dhcpcd: add recipe for dhcpcd

 

 

On 10 December 2015 at 03:36, Nate Karstens <nate.karstens@garmin.com> wrote:

Adds a new recipe for dhcpcd. Modifies the configure script to keep the
host system header files from being used instead of the target system.

Signed-off-by: Nate Karstens <nate.karstens@garmin.com>


For new recipes to be added to oe-core there needs to be a good rationale.  It seems that this is very well suited for the meta-networking layer (part of meta-oe).

 

Ross



CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.