All of lore.kernel.org
 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: Fri, 15 Jul 2011 09:43:07 -0500	[thread overview]
Message-ID: <4E2051FB.8080006@windriver.com> (raw)
In-Reply-To: <1310740753.2350.0.camel@scimitar>

On 7/15/11 9:39 AM, Joshua Lock wrote:
> On Thu, 2011-07-14 at 21:56 -0500, Mark Hatle wrote:
>> 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.
> 
> Originally I built chrpath when I added relocatable.bbclass but then we
> wanted to relocate native packages and it got extremely tricky...

I wonder if we can do something like pseudo and force chrpath to be built -very-
early in the process.. and then have most things have an automatic requirement
on chrpath-native...

(pseudo of course has the advantage it's NOT used for native packages...)

Is the native chrpath usage only in do_package [or later]?  If so, we could
probably put a dependency on do_package of chrpath.. with the affect that
chrpath would have to be built first...

--Mark

> 
> Joshua




  reply	other threads:[~2011-07-15 14:47 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
2011-07-15 14:39   ` Joshua Lock
2011-07-15 14:43     ` Mark Hatle [this message]
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=4E2051FB.8080006@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.