From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2 2/2] Indent: Add new recipe
Date: Fri, 21 Nov 2014 10:52:30 +0100 [thread overview]
Message-ID: <20141121095230.GA2163@jama> (raw)
In-Reply-To: <1416556558-15428-3-git-send-email-qianl.fnst@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]
On Fri, Nov 21, 2014 at 03:55:58PM +0800, Qian Lei wrote:
> Indent is a GNU program for beautifying C code, so that it is easier
> to read. Indent can also convert from one C writing style to a different
> one. Indent understands correct C syntax and tries to handle incorrect C
> syntax.
>
> Signed-off-by: Qian Lei <qianl.fnst@cn.fujitsu.com>
> ---
> meta-oe/recipes-extended/indent/indent_2.2.10.bb | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
> create mode 100644 meta-oe/recipes-extended/indent/indent_2.2.10.bb
>
> diff --git a/meta-oe/recipes-extended/indent/indent_2.2.10.bb b/meta-oe/recipes-extended/indent/indent_2.2.10.bb
> new file mode 100644
> index 0000000..df40cc0
> --- /dev/null
> +++ b/meta-oe/recipes-extended/indent/indent_2.2.10.bb
> @@ -0,0 +1,22 @@
> +SUMMARY = "A GNU program for formatting C code"
> +HOMEPAGE = "http://www.gnu.org/software/indent/"
> +SECTION = "Applications/Text"
> +DESCRIPTION = "Indent is a GNU program for beautifying C code, so that \
> +it is easier to read. Indent can also convert from one C writing style \
> +to a different one. Indent understands correct C syntax and tries to handle \
> +incorrect C syntax. \
> +Install the indent package if you are developing applications in C and \
> +you want a program to format your code."
> +LICENSE = "GPL-2.0"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
> +DEPENDS = "virtual/gettext"
> +
> +SRC_URI = "${GNU_MIRROR}/indent/${BP}.tar.gz"
indent -> BPN
> +SRC_URI[md5sum] = "be35ea62705733859fbf8caf816d8959"
> +SRC_URI[sha256sum] = "8a9b41be5bfcab5d8c1be74204b10ae78789fc3deabea0775fdced8677292639"
> +
> +inherit autotools gettext
> +
> +FILES_${PN} += "/usr/doc/indent/indent.html"
shouldn't this be installed in /usr/share/doc ($docdir)?
and should it be included in $PN or $PN-doc?
Also move this change before umip which is using it.
> +
> +BBCLASSEXTEND = "native"
> --
> 1.8.3.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:[~2014-11-21 9:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 9:51 [PATCH] umip: Add new recipes Qian Lei
2014-11-19 15:49 ` Martin Jansa
2014-11-21 7:55 ` [PATCH v2 0/2] Add new recipe UMIP & Indent Qian Lei
2014-11-21 7:55 ` [PATCH v2 1/2] UMIP: add new recipe Qian Lei
2014-11-21 14:06 ` Joe MacDonald
2014-11-21 14:19 ` Martin Jansa
2014-11-21 14:46 ` Joe MacDonald
2014-11-25 9:23 ` Qian Lei
2014-11-21 7:55 ` [PATCH v2 2/2] Indent: Add " Qian Lei
2014-11-21 9:52 ` Martin Jansa [this message]
2014-11-24 5:21 ` [PATCH v3 1/2] indent: " Qian Lei
2014-11-24 5:28 ` [PATCH v3 2/2] UMIP: add " Qian Lei
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=20141121095230.GA2163@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.