From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: help2man
Date: Thu, 29 Sep 2011 12:58:54 +0100 [thread overview]
Message-ID: <1317297541.12332.85.camel@ted> (raw)
The more I look at and think about help2man, the more it looks like
something we just shouldn't need/use.
In summary, it runs a binary and captures its --help output. This rules
it out from being useful in most cross compiling scenarios, i.e. all
target packages.
In the -native/-cross cases, we don't really care about man pages.
I'm therefore thinking we should really just drop the dependency and
symlink help2man to /bin/false. The missing script in autotools should
then just silently touch the man page files instead of regenerating
them.
I tried to figure out which recipes actually use help2man:
$ grep HELP2MAN * -r --exclude=Makefile.in 2> /dev/null | grep -v missing
and against a core-image-sato this gave:
libtool
libtasn1
gettext
automake
autoconf
flex
bison
m4
which isn't that many recipes to go and beat up manually if necessary.
It certainly doesn't warrant a global include in autotools.bbclass IMO.
Cheers,
Richard
next reply other threads:[~2011-09-29 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 11:58 Richard Purdie [this message]
2011-10-03 19:06 ` help2man Khem Raj
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=1317297541.12332.85.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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