From: Denys Dmytriyenko <denys@ti.com>
To: Sam Nelson <sam.nelson@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [PATCH] lksctp-tools: Add new recipe for lksctp tools: library and utilities
Date: Mon, 15 Dec 2014 14:15:04 -0500 [thread overview]
Message-ID: <20141215191504.GD28600@edge> (raw)
In-Reply-To: <1418667057-19653-1-git-send-email-sam.nelson@ti.com>
On Mon, Dec 15, 2014 at 01:10:57PM -0500, Sam Nelson wrote:
> - Stream Control Transmission Protocol (SCTP) is a reliable, message-oriented,
> multihomed transport protocol. Developed by the IETF SIGTRAN working group
> to transport SS7 over IP, it is now the third general-purpose transport developed
> by the IETF.
Looks fine to me. Please see below for 1 small question.
> Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> ---
> .../lksctp-tools/lksctp-tools_1.0.16.bb | 44 ++++++++++++++++++++
> 1 file changed, 44 insertions(+)
> create mode 100755 meta-arago-extras/recipes-connectivity/lksctp-tools/lksctp-tools_1.0.16.bb
>
> diff --git a/meta-arago-extras/recipes-connectivity/lksctp-tools/lksctp-tools_1.0.16.bb b/meta-arago-extras/recipes-connectivity/lksctp-tools/lksctp-tools_1.0.16.bb
> new file mode 100755
> index 0000000..3765715
> --- /dev/null
> +++ b/meta-arago-extras/recipes-connectivity/lksctp-tools/lksctp-tools_1.0.16.bb
> @@ -0,0 +1,44 @@
> +DESCRIPTION = "The Linux Kernel Stream Control Transmission Protocol (lksctp) project"
> +SECTION = "libs"
> +PRIORITY = "optional"
> +LICENSE = "LGPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=0c56db0143f4f80c369ee3af7425af6e"
> +
> +PR = "r0"
> +
> +SRC_URI = "${SOURCEFORGE_MIRROR}/lksctp/lksctp-tools-${PV}.tar.gz"
> +
> +SRC_URI[md5sum] = "708bb0b5a6806ad6e8d13c55b067518e"
> +SRC_URI[sha256sum] = "0903dd526b7f30a89d5031aa2c82757612becc38ed7bc6e4f972f8deae351f26"
> +
> +BBCLASSEXTEND = "native"
> +
> +inherit autotools pkgconfig binconfig
> +
> +RREPLACES_${PN} = "lksctp"
> +
> +PACKAGES =+ "${PN}-utils"
> +
> +FILES_${PN} = "${libexecdir}/* ${libdir}/lib*${SOLIBS} \
> + ${sysconfdir} ${sharedstatedir} ${localstatedir} \
> + ${base_libdir}/*${SOLIBS}"
> +
> +FILES_${PN}-dev += " \
> + ${datadir}/lksctp-tools/checksctp.c \
> + ${datadir}/lksctp-tools/sctp_socket.c \
> + ${datadir}/lksctp-tools/sctp_bind.c \
> + ${datadir}/lksctp-tools/sctp_darn.c \
> + ${datadir}/lksctp-tools/sctp_load_libs.c \
> + ${datadir}/lksctp-tools/sctp_sockopt.c \
> + ${datadir}/lksctp-tools/sctp_socket.h \
> + ${datadir}/lksctp-tools/sctp_test.c \
> + ${datadir}/lksctp-tools/sctp_darn.h \
> + ${datadir}/lksctp-tools/sctp_status.c \
> + ${libdir}/lksctp-tools/lib*.so"
The last line above lists all lib*.so in lksctp-tools off of libdir - are
those real libraries and do you need to list them in the main package too?
> +
> +FILES_${PN}-utils = " \
> + ${bindir}/sctp_test \
> + ${bindir}/sctp_darn \
> + ${bindir}/checksctp \
> + ${bindir}/withsctp \
> + ${bindir}/sctp_status"
> --
> 1.7.9.5
>
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
next prev parent reply other threads:[~2014-12-15 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 18:10 [PATCH] lksctp-tools: Add new recipe for lksctp tools: library and utilities Sam Nelson
2014-12-15 19:15 ` Denys Dmytriyenko [this message]
2014-12-16 15:40 ` Nelson, Sam
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=20141215191504.GD28600@edge \
--to=denys@ti.com \
--cc=meta-arago@arago-project.org \
--cc=sam.nelson@ti.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.