From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] devtools: add a bb for git-manpages
Date: Fri, 30 Jan 2015 19:08:25 -0500 [thread overview]
Message-ID: <1422662905-3598-1-git-send-email-paul.gortmaker@windriver.com> (raw)
These could be created from scratch from git itself, but it
requires asciidoc, xsltproc, python bits and too much other
baggage. Since the git folks issue a tarball with the manpages
for each release, it is simpler to just go get that.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
---
.../git-manpages/git-manpages_2.2.1.bb | 25 ++++++++++++++++++++++
1 file changed, 25 insertions(+)
create mode 100644 meta/recipes-devtools/git-manpages/git-manpages_2.2.1.bb
diff --git a/meta/recipes-devtools/git-manpages/git-manpages_2.2.1.bb b/meta/recipes-devtools/git-manpages/git-manpages_2.2.1.bb
new file mode 100644
index 000000000000..7d8e0e972738
--- /dev/null
+++ b/meta/recipes-devtools/git-manpages/git-manpages_2.2.1.bb
@@ -0,0 +1,25 @@
+SUMMARY = "Distributed version control system manpages"
+SECTION = "console/utils"
+LICENSE = "GPLv2"
+DEPENDS = "git"
+
+RDEPENDS_${PN} = "git"
+SRC_URI = "https://www.kernel.org/pub/software/scm/git/git-manpages-${PV}.tar.gz"
+
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
+
+SRC_URI[md5sum] = "b5ddd262b608804ba4403f0f82d881d7"
+SRC_URI[sha256sum] = "69dcb3decdb33dd35491935e80f71c40c576b536df4223eb98d5f7ccd9643293"
+
+FILES_${PN}-doc = "${mandir}"
+
+do_configure () {
+}
+
+do_compile () {
+}
+
+do_install () {
+ mkdir -p ${D}/${mandir}
+ cp -a ${WORKDIR}/man[1-9] ${D}/${mandir}
+}
--
2.2.1
next reply other threads:[~2015-01-31 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 0:08 Paul Gortmaker [this message]
2015-02-02 17:04 ` [PATCH] devtools: add a bb for git-manpages Paul Eggleton
2015-02-02 20:54 ` Paul Gortmaker
2015-02-03 9:45 ` Paul Eggleton
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=1422662905-3598-1-git-send-email-paul.gortmaker@windriver.com \
--to=paul.gortmaker@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