public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: <mingli.yu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 3/4] file-which-perl: add new recipe
Date: Fri, 26 Aug 2016 10:25:48 +0800	[thread overview]
Message-ID: <1472178349-32199-4-git-send-email-mingli.yu@windriver.com> (raw)
In-Reply-To: <1472178349-32199-1-git-send-email-mingli.yu@windriver.com>

From: Mingli Yu <Mingli.Yu@windriver.com>

* Add file-which-perl recipe as file-homedir-perl
  rdepends on file-which-perl

Signed-off-by: Mingli Yu <Mingli.Yu@windriver.com>
---
 meta/recipes-devtools/perl/file-which-perl_1.21.bb | 27 ++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 meta/recipes-devtools/perl/file-which-perl_1.21.bb

diff --git a/meta/recipes-devtools/perl/file-which-perl_1.21.bb b/meta/recipes-devtools/perl/file-which-perl_1.21.bb
new file mode 100644
index 0000000..ac9c0e5
--- /dev/null
+++ b/meta/recipes-devtools/perl/file-which-perl_1.21.bb
@@ -0,0 +1,27 @@
+DESCRIPTION = "File::Which finds the full or relative paths to executable programs on the \
+system. This is normally the function of "which" utility. "which" is \
+typically implemented as either a program or a built in shell command. On \
+some platforms, such as Microsoft Windows it is not provided as part of the \
+core operating system. This module provides a consistent API to this \
+functionality regardless of the underlying platform."
+
+SECTION = "libs"
+LICENSE = "Artisticv1 | GPLv1+"
+PR = "r0"
+
+MAINTAINER=	"Poky <poky@yoctoproject.org>"
+HOMEPAGE=	"https://metacpan.org/release/File-Which"
+
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/Artistic-1.0;md5=cda03bbdc3c1951996392b872397b798 \
+file://${COMMON_LICENSE_DIR}/GPL-1.0;md5=e9e36a9de734199567a4d769498f743d"
+
+SRC_URI = "https://cpan.metacpan.org/authors/id/P/PL/PLICEASE/File-Which-${PV}.tar.gz"
+
+SRC_URI[md5sum] = "115a6efe5d7e9621237fcb655c7a0980"
+SRC_URI[sha256sum] = "9def5f10316bfd944e56b7f8a2501be1d44c288325309462aa9345e340854bcc"
+
+S = "${WORKDIR}/File-Which-${PV}"
+
+inherit cpan
+
+BBCLASSEXTEND = "native"
-- 
2.8.1



  parent reply	other threads:[~2016-08-26  2:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26  2:25 [PATCH 0/4] groff: add file-homedir-perl to RDEPENDS mingli.yu
2016-08-26  2:25 ` [PATCH 1/4] " mingli.yu
2016-08-26  2:25 ` [PATCH 2/4] file-homedir-perl: add new recipe mingli.yu
2016-08-26  2:25 ` mingli.yu [this message]
2016-08-26  2:25 ` [PATCH 4/4] extutils-makemaker-perl: " mingli.yu
2016-08-26  8:55 ` [PATCH 0/4] groff: add file-homedir-perl to RDEPENDS Burton, Ross
2016-08-26  9:28   ` Yu, Mingli
2016-09-02  1:54     ` Yu, Mingli
2016-09-02 11:41       ` Richard Purdie
2016-09-05  1:50         ` Yu, Mingli

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=1472178349-32199-4-git-send-email-mingli.yu@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=openembedded-core@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