From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] devtools: add a bb for git-manpages
Date: Mon, 2 Feb 2015 15:54:30 -0500 [thread overview]
Message-ID: <20150202205429.GC3394@windriver.com> (raw)
In-Reply-To: <5253630.c2vWHxRG0u@peggleto-mobl5.ger.corp.intel.com>
[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
next prev parent reply other threads:[~2015-02-02 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 0:08 [PATCH] devtools: add a bb for git-manpages Paul Gortmaker
2015-02-02 17:04 ` Paul Eggleton
2015-02-02 20:54 ` Paul Gortmaker [this message]
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=20150202205429.GC3394@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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