From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: CALL FOR ACTION: get rid of native recipes
Date: Tue, 03 Aug 2010 13:46:42 +0100 [thread overview]
Message-ID: <1280839602.16235.69.camel@rex> (raw)
In-Reply-To: <A6DDF661-1A0C-444D-BA84-9E7116031A3E@vanille-media.de>
On Tue, 2010-08-03 at 10:21 +0200, Dr. Michael Lauer wrote:
> that's pretty cool, however I think we should restrict this list
> to those recipes which also have a non-native variant.
>
> E.g. the 2nd entry in this list is android-image-utils-native for
> which a non-native variant makes little sense.
Just to add, there are some cases where the -native recipe still makes
sense as the alternative is rather ugly for example, python-native,
perl-native and a handful of others. The number of these cases is
extremely small however. BBCLASSEXTEND makes sense in most cases.
Cheers,
Richard
next prev parent reply other threads:[~2010-08-03 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 20:28 CALL FOR ACTION: get rid of native recipes Frans Meulenbroeks
2010-08-03 8:21 ` Dr. Michael Lauer
2010-08-03 9:17 ` Frans Meulenbroeks
2010-08-03 12:46 ` Richard Purdie [this message]
2010-08-03 13:58 ` Dr. Michael Lauer
2010-08-04 0:03 ` Denys Dmytriyenko
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=1280839602.16235.69.camel@rex \
--to=rpurdie@rpsys.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox