From: Tom Rini <trini@konsulko.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 1/2] libfile-fnmatch-perl: New recipe
Date: Sun, 11 Jun 2017 13:02:04 -0400 [thread overview]
Message-ID: <20170611170204.GU10782@bill-the-cat> (raw)
In-Reply-To: <CAMKF1srsu4Aq=aPVwCCCQynDNz5uPe1MsaasP7Mrx4oXm=MS4A@mail.gmail.com>
On Sun, Jun 11, 2017 at 08:59:49AM -0700, Khem Raj wrote:
> On Sun, Jun 11, 2017 at 8:06 AM, Tom Rini <trini@konsulko.com> wrote:
> > File::FnMatch::fnmatch() provides simple, shell-like pattern matching.
> >
> > Though considerably less powerful than regular expressions, shell patterns
> > are nonetheless useful and familiar to a large audience of end-users.
> >
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > .../perl/libfile-fnmatch-perl_0.02.bb | 22 ++++++++++++++++++++++
> > 1 file changed, 22 insertions(+)
> > create mode 100644 meta-oe/recipes-extended/perl/libfile-fnmatch-perl_0.02.bb
> >
> > diff --git a/meta-oe/recipes-extended/perl/libfile-fnmatch-perl_0.02.bb b/meta-oe/recipes-extended/perl/libfile-fnmatch-perl_0.02.bb
>
> may be meta-perl is better suited for this
I only hesitate because I don't think debsums then belongs in meta-perl.
I took the existing example of a few other libfoo-perl recipes as being
appropriate for here. Thanks!
--
Tom
prev parent reply other threads:[~2017-06-11 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 15:06 [meta-oe][PATCH 1/2] libfile-fnmatch-perl: New recipe Tom Rini
2017-06-11 15:06 ` [meta-oe][PATCH 2/2] debsums: " Tom Rini
2017-06-11 15:59 ` Khem Raj
2017-06-11 16:59 ` Tom Rini
2017-06-11 17:20 ` Khem Raj
2017-06-11 19:05 ` Tom Rini
2017-06-12 13:53 ` [meta-oe][PATCHv2 " Tom Rini
2017-06-11 15:59 ` [meta-oe][PATCH 1/2] libfile-fnmatch-perl: " Khem Raj
2017-06-11 17:02 ` Tom Rini [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=20170611170204.GU10782@bill-the-cat \
--to=trini@konsulko.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox