All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Finishing packaged-staging (this version..)
Date: Tue, 27 Jul 2010 16:35:37 -0700	[thread overview]
Message-ID: <4C4F6D49.8080303@mentor.com> (raw)
In-Reply-To: <4C45E471.5070004@mentor.com>

Tom Rini wrote:
> Hey all,
> 
> As Koen mentioned in another thread, packaged-staging is "halfway done". 
>  So, what's left to get things done good enough for now?  From my point 
> of view it's:
> - Need to get binconfig scripts into the target directory
> - Need to $ORIGIN cross tools
> 
> Once that's done we should have fully relocatable pstaging packages and 
> at that point we can talk about how to do things better.
> 
> poky currently has both of these done, and it involves killing the cross 
> directory (roughly, moving it to sysroots/${HOST_OS}).
> 
> Anyone see anything else needed before we can have a pstaging that's 
> functional enough to use as a baseline for rework?
> 
> Richard, any chance someone from your team is going to be working on 
> rebasing your changes against oe.dev soon?

So, given that Khem did the above needed pulling from poky (and exposed 
an issue with it that's being dealt with now), I think this version of 
packaged staging is done.  I'm doing some torture builds currently, but 
the only issue I can think of, at a "doesn't work" level is wrt 
guile-native and I'll RFC a fix for that shortly.  Oh, and perl-native 
is another story I'll RFC in a moment.

-- 
Tom Rini
Mentor Graphics Corporation



      reply	other threads:[~2010-07-27 23:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 18:01 Finishing packaged-staging (this version..) Tom Rini
2010-07-27 23:35 ` Tom Rini [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=4C4F6D49.8080303@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@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.