All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Improve handling of 'all' architecture recipes and their interaction with sstate
Date: Fri, 30 Sep 2011 18:09:31 +0100	[thread overview]
Message-ID: <1317402578.12332.218.camel@ted> (raw)
In-Reply-To: <20110930164658.GB7364@jama.jama.net>

On Fri, 2011-09-30 at 18:46 +0200, Martin Jansa wrote:
> On Fri, Sep 30, 2011 at 03:15:15PM +0100, Richard Purdie wrote:
> > I'd not forgotten about this patch, just been distracted by other
> > things. I've run some further tests on the changes here and have
> > comments below. Summary is I think some pieces can merge, other pieces
> > need more work. Lets try and get the pieces that are ready merged, then
> > worry about the remainder.
> > 
> > Could we clean out the problematic pieces and resubmit please so we can
> > at least get those pieces in? :)
> 
> pushed as 6 patches to 
> oe-core-contrib jansa/allarch
> 
> 1st patch contains changes you've marked as fine
> 2nd is hal-info, which is imho not worth debugging it as nobody likes
>   hal nowadays (I've tried to patch configure.in, but recipe doesn't
>   call reautoconf IIRC..)
> the rest is kept as reminder which recipes needs to be taken care of.

Thanks. I've taken the two patches. I'd love to get rid of hal, in fact
its on my list of things that need to migrate out of OE-Core...

I'm left wondering what (if anything) uses hal in our images?

Cheers,

Richard




  reply	other threads:[~2011-09-30 17:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30  8:19 [PATCH] Improve handling of 'all' architecture recipes and their interaction with sstate Martin Jansa
2011-09-30 14:15 ` Richard Purdie
2011-09-30 16:46   ` Martin Jansa
2011-09-30 17:09     ` Richard Purdie [this message]
2011-09-30 17:12       ` Martin Jansa
2011-10-01 18:48       ` Otavio Salvador
2011-10-04 22:00         ` Richard Purdie
2011-10-04 22:18           ` Koen Kooi
2011-10-05 12:10           ` Otavio Salvador
2011-10-05 12:22             ` Koen Kooi
2011-10-05 12:27               ` Otavio Salvador
2011-10-05 12:29                 ` Koen Kooi
2011-10-05 12:34                   ` Martin Jansa
2011-10-05 13:02                     ` Richard Purdie
2011-10-05 19:32                       ` Khem Raj
2011-10-01 18:46 ` Otavio Salvador

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=1317402578.12332.218.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=martin.jansa@gmail.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.