From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: help2man update
Date: Fri, 14 Dec 2012 14:42:23 -0600 [thread overview]
Message-ID: <50CB8F2F.7050405@windriver.com> (raw)
In-Reply-To: <1355512785-6255-1-git-send-email-cazfi74@gmail.com>
On 12/14/12 1:19 PM, Marko Lindqvist wrote:
>
> As part of systematic check for newer versions of GNU packages
> I noticed this one, and it turned out to build as trivial
> update (change version number, PR, checksums). But is help2man
> actually used for anything? Many components that use it in
> their upstream have patch to disable it in oe builds.
It is unfortunately needed to build a number of things. In addition, we do want
to have working man pages available for some configurations. So this uprev
looks like a very good idea to me.
--Mark
>
>
> - ML
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2012-12-14 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 19:19 help2man update Marko Lindqvist
2012-12-14 19:19 ` [PATCH] help2man: update to upstream version 1.40.13 Marko Lindqvist
2012-12-14 20:42 ` Mark Hatle [this message]
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=50CB8F2F.7050405@windriver.com \
--to=mark.hatle@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