[oe] [RFC, PATCH] Make packaged-staging use more correct PSTAGE_PKGARCH

[Chris Larson]

On Wed, Jun 23, 2010 at 10:24 AM, Khem Raj <raj.khem at gmail.com> wrote:

> On (22/06/10 11:55), Tom Rini wrote:
> > Khem Raj wrote:
> > >On (21/06/10 14:54), Tom Rini wrote:
> > >>packaged-staging.bbclass: Change PSTAGE_PKGARCH to something dynamic
> > >>
> > >>Currently, we make all pstage packages be locked to BUILD_SYS which
> > >>causes annoying warnings in some cases and doesn't allow for sharing
> > >>between say 32 and 64bit (which is valid for target bits).
> > >>
> > >>This changes to ${PACKAGE_ARCH}-${HOST_SYS} for everything and
> > >>reworks the opkg.conf we generate to add entries as needed.
> > >>
> > >>There is an alternative, suggested by Chris Larson, that we modify
> > >>PSTAGE_PKGARCH in an anon python function so that we can avoid
> > >>things like 'x86_64-x86_64-linux' in native packages and similar
> > >>duplication in sdk packages, or otherwise be more dynamic (use
> > >>HOST_OS instead of SYS and then catch the cross case, etc).
> > >
> > >I think this approach sounds better having same arch repeated twice
> > >would be confusing
> >
> > Here we go.  This also reworks generating opkg.conf a little bit (it
> > had multiple entries before due to a lazy grep).
> >
> > Signed-off-by: Tom Rini <tom_rini at mentor.com>
>
> very nice
>
> Acked-by: Khem Raj <raj.khem at gmail.com>


Acked-by: Chris Larson <chris_larson at mentor.com>
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics