[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 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
