[PATCH] devtools: add a bb for git-manpages

[PATCH] devtools: add a bb for git-manpages

[Paul Gortmaker]

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

Re: [PATCH] devtools: add a bb for git-manpages

[Paul Eggleton]

Hi Paul,

On Friday 30 January 2015 19:08:25 Paul Gortmaker wrote:
> 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.

I'm just wondering, would it be simpler to just do this as part of the git 
recipe itself and have the manpages go into git-doc? Then you would get the 
documentation automatically if you had git in your image and doc-pkgs in 
IMAGE_FEATURES, plus we wouldn't have to remember to upgrade this every time 
we upgraded the git recipe.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: [PATCH] devtools: add a bb for git-manpages

[Paul Gortmaker]

[Re: [OE-core] [PATCH] devtools: add a bb for git-manpages] On 02/02/2015 (Mon 17:04) Paul Eggleton wrote:

> Hi Paul,
> 
> On Friday 30 January 2015 19:08:25 Paul Gortmaker wrote:
> > 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.
> 
> I'm just wondering, would it be simpler to just do this as part of the git 
> recipe itself and have the manpages go into git-doc? Then you would get the 
> documentation automatically if you had git in your image and doc-pkgs in 
> IMAGE_FEATURES, plus we wouldn't have to remember to upgrade this every time 
> we upgraded the git recipe.

I'm sure we can do that if desired.  It is probably worth mentioning
that I had this standalone recipe off in a layer for a while, and after
discussions on how to deal with coreutils and the mess it creats with
the openly hostile to cross-compile "help2man" that the idea of a
separate bb for manpages appeared acceptable.  So, based on that, I
figured it was time to post my git-manpages bb.

This brings me back to coreutils -- should we source prebuilt manpages
within the main recipe there too, or do a coreutils-manpages.bb  ?

P.
--

> 
> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre

Re: [PATCH] devtools: add a bb for git-manpages

[Paul Eggleton]

On Monday 02 February 2015 15:54:30 Paul Gortmaker wrote:
> [Re: [OE-core] [PATCH] devtools: add a bb for git-manpages] On 02/02/2015 
(Mon 17:04) Paul Eggleton wrote:
> > On Friday 30 January 2015 19:08:25 Paul Gortmaker wrote:
> > > 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.
> > 
> > I'm just wondering, would it be simpler to just do this as part of the git
> > recipe itself and have the manpages go into git-doc? Then you would get
> > the documentation automatically if you had git in your image and doc-pkgs
> > in IMAGE_FEATURES, plus we wouldn't have to remember to upgrade this every
> > time we upgraded the git recipe.
> 
> I'm sure we can do that if desired.  It is probably worth mentioning
> that I had this standalone recipe off in a layer for a while, and after
> discussions on how to deal with coreutils and the mess it creats with
> the openly hostile to cross-compile "help2man" that the idea of a
> separate bb for manpages appeared acceptable.  So, based on that, I
> figured it was time to post my git-manpages bb.

I just think if upstream ships pre-generated docs in lock-step with its code 
releases, we might as well fetch and package them up as part of the normal 
recipe and save ourselves some maintenance.
 
> This brings me back to coreutils -- should we source prebuilt manpages
> within the main recipe there too, or do a coreutils-manpages.bb  ?

The same applies there too I would think.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre