Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Building hg/help2man not relying on them?
Date: Thu, 14 Jul 2011 21:56:26 -0500	[thread overview]
Message-ID: <4E1FAC5A.2090308@windriver.com> (raw)
In-Reply-To: <4E1F9F59.5050305@mentor.com>

On 7/14/11 9:00 PM, Tom Rini wrote:
> Hey all,
> 
> As I work on bringing jenkins up on my stripped down builder machines
> I've once again run into the "wait, I'm supposed to have installed...?"
> problem.  Can we switch to building help2man and mercurial rather than
> making the end user install them?  Perhaps some sort of test for if we
> find it, ASSUME_PROVIDED it, otherwise build it?
> 

The full sanity list is:

patch help2man diffstat texi2html makeinfo cvs svn bzip2 tar gzip gawk hg
chrpath wget cpio

Of the above, help2man, texi2html, hg, and chrpath seem to be the ones I usually
have to find or build myself.

If we can build those (or setup the assume_provide) that would make it much
easier for me....

--Mark



  reply	other threads:[~2011-07-15  3:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  2:00 Building hg/help2man not relying on them? Tom Rini
2011-07-15  2:56 ` Mark Hatle [this message]
2011-07-15 14:39   ` Joshua Lock
2011-07-15 14:43     ` Mark Hatle
2011-07-15 15:08       ` Tom Rini
2011-07-15 15:18         ` Phil Blundell
2011-07-15 15:23           ` Richard Purdie
2011-07-15 15:38             ` Phil Blundell
2011-07-15 15:44               ` Phil Blundell
2011-07-15 18:09         ` Tom Rini

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=4E1FAC5A.2090308@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