From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH v4] dhcpcd: add recipe for dhcpcd
Date: Wed, 27 Jan 2016 15:15:49 +0100 [thread overview]
Message-ID: <20160127141549.GG2574@jama> (raw)
In-Reply-To: <1452726499-3950-1-git-send-email-nate.karstens@garmin.com>
[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]
On Wed, Jan 13, 2016 at 05:08:19PM -0600, Nate Karstens wrote:
> Adds a new recipe for dhcpcd version 6.10.0.
It was merged, but there is QA warning:
dhcpcd-6.9.4: dhcpcd rdepends on libudev, but it isn't a build dependency? [build-deps]
Please send follow-up patch to fix this.
> Signed-off-by: Nate Karstens <nate.karstens@garmin.com>
> ---
> .../recipes-connectivity/dhcpcd/dhcpcd_6.10.0.bb | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
> create mode 100644 meta-networking/recipes-connectivity/dhcpcd/dhcpcd_6.10.0.bb
>
> diff --git a/meta-networking/recipes-connectivity/dhcpcd/dhcpcd_6.10.0.bb b/meta-networking/recipes-connectivity/dhcpcd/dhcpcd_6.10.0.bb
> new file mode 100644
> index 0000000..058a932
> --- /dev/null
> +++ b/meta-networking/recipes-connectivity/dhcpcd/dhcpcd_6.10.0.bb
> @@ -0,0 +1,22 @@
> +SECTION = "console/network"
> +SUMMARY = "dhcpcd - a DHCP client"
> +DESCRIPTION = "dhcpcd runs on your machine and silently configures your computer to work on the attached networks without trouble and mostly without configuration."
> +
> +HOMEPAGE = "http://roy.marples.name/projects/dhcpcd/"
> +
> +LICENSE = "BSD-2-Clause"
> +LIC_FILES_CHKSUM = "file://dhcpcd.c;endline=26;md5=77c40d671aff804ca91ea99556da8e9b"
> +
> +SRC_URI = "http://roy.marples.name/downloads/${BPN}/${BPN}-${PV}.tar.xz"
> +
> +SRC_URI[md5sum] = "f39c5773e7c4bea352d9fb7367c899de"
> +SRC_URI[sha256sum] = "ab56af9b2e86913c55a965cb0f835e87749df78318564acf90d5d698f413ad35"
> +
> +inherit autotools
> +
> +B = "${S}"
> +EXTRA_OECONF = "--enable-ipv4 --enable-ipv6"
> +
> +FILES_${PN}-dbg += "${libdir}/dhcpcd/dev/.debug"
> +
> +RDEPENDS_${PN} = "udev"
> --
> 1.9.1
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-01-27 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 23:08 [meta-networking][PATCH v4] dhcpcd: add recipe for dhcpcd Nate Karstens
2016-01-27 14:15 ` Martin Jansa [this message]
2016-01-29 1:21 ` Karstens, Nate
2016-03-02 2:35 ` Stephen Arnold
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=20160127141549.GG2574@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.