From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/3][meta-perl] libxml-filter-buffertext-perl: add recipe
Date: Wed, 16 Jul 2014 16:03:41 +0200 [thread overview]
Message-ID: <20140716140341.GC2433@jama> (raw)
In-Reply-To: <1405058909-12162-1-git-send-email-rongqing.li@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]
On Fri, Jul 11, 2014 at 02:08:29PM +0800, rongqing.li@windriver.com wrote:
> From: Roy Li <rongqing.li@windriver.com>
>
> Signed-off-by: Roy Li <rongqing.li@windriver.com>
> ---
> .../libxml/libxml-filter-buffertext-perl_1.01.bb | 27 ++++++++++++++++++++
> 1 file changed, 27 insertions(+)
> create mode 100644 meta-perl/recipes-perl/libxml/libxml-filter-buffertext-perl_1.01.bb
>
> diff --git a/meta-perl/recipes-perl/libxml/libxml-filter-buffertext-perl_1.01.bb b/meta-perl/recipes-perl/libxml/libxml-filter-buffertext-perl_1.01.bb
> new file mode 100644
> index 0000000..0fbeeb5
> --- /dev/null
> +++ b/meta-perl/recipes-perl/libxml/libxml-filter-buffertext-perl_1.01.bb
> @@ -0,0 +1,27 @@
> +SUMMARY = "XML::Filter::BufferText - Filter to put all characters() in one event"
> +DESCRIPTION = "\
> +The XML::Filter::BufferText module is a very simple filter. One common \
> +cause of grief (and programmer error) is that XML parsers aren't required \
> +to provide character events in one chunk. They can, but are not forced \
> +to, and most don't. This filter does the trivial but oft-repeated task \
> +of putting all characters into a single event. \
> +"
> +SECTION = "libs"
> +LICENSE = "Artistic-1.0 | GPLv1+"
> +HOMEPAGE = "http://search.cpan.org/dist/XML-Filter-BufferText/"
> +DEPENDS += "libxml-sax-perl-native"
> +RDEPENDS_${PN} += "libxml-sax-perl"
> +
> +SRC_URI = "http://search.cpan.org/CPAN/authors/id/R/RB/RBERJON/XML-Filter-BufferText-${PV}.tar.gz"
> +SRC_URI[md5sum] = "2992c0387632583b966ab9c965b25512"
> +SRC_URI[sha256sum] = "8fd2126d3beec554df852919f4739e689202cbba6a17506e9b66ea165841a75c"
> +
> +LIC_FILES_CHKSUM = "file://BufferText.pm;beginline=88;endline=90;md5=497aa6d79cc84c3d769a2a0016bee928"
> +
> +S = "${WORKDIR}/XML-Filter-BufferText-${PV}"
> +
> +inherit cpan
> +
> +BBCLASSEXTEND = "native"
> +
> +PACKAGE_ARCH = "all"
This doesn't seem right, see
http://lists.openembedded.org/pipermail/openembedded-core/2014-July/094409.html
--
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-07-16 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 6:08 [PATCH 2/3][meta-perl] libxml-filter-buffertext-perl: add recipe rongqing.li
2014-07-14 1:50 ` Hongxu Jia
2014-07-16 14:03 ` Martin Jansa [this message]
2014-07-17 12:29 ` Rongqing Li
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=20140716140341.GC2433@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox