From: "Karstens, Nate" <Nate.Karstens@garmin.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] dhcpcd: add recipe for dhcpcd
Date: Tue, 22 Dec 2015 21:30:55 +0000 [thread overview]
Message-ID: <145451D4E6785E4DA4DFA353A58CB7B2F7E4C625@OLAWPA-EXMB03.ad.garmin.com> (raw)
In-Reply-To: <CAJTo0LbQJFobJgJVP5qDHxATgfz3i7V+h1De1+PY627Zpgr-eQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
Sounds good. I’ll resubmit to meta-networking. Once that goes through I’ll submit a patch to remove it from meta-alt-desktop-extras.
Thanks,
Nate
From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Tuesday, December 22, 2015 3:20 PM
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 22 December 2015 at 17:13, Karstens, Nate <Nate.Karstens@garmin.com<mailto:Nate.Karstens@garmin.com>> wrote:
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.
Definitely (2), oe-core needs *something* to provide DHCP functionality but meta-networking is the obvious fit for an alternative choice.
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.
[-- Attachment #2: Type: text/html, Size: 5556 bytes --]
prev parent reply other threads:[~2015-12-22 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 3:36 [PATCH] dhcpcd: add recipe for dhcpcd Nate Karstens
2015-12-22 17:04 ` Burton, Ross
2015-12-22 17:13 ` Karstens, Nate
2015-12-22 21:20 ` Burton, Ross
2015-12-22 21:30 ` Karstens, Nate [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=145451D4E6785E4DA4DFA353A58CB7B2F7E4C625@OLAWPA-EXMB03.ad.garmin.com \
--to=nate.karstens@garmin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.