From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: RFC: nativesdk and native recipe names
Date: Wed, 21 Dec 2011 12:59:59 +0000 [thread overview]
Message-ID: <1324472399.16323.26.camel@ted> (raw)
In-Reply-To: <20111221115728.GA6198@ad.chargestorm.se>
On Wed, 2011-12-21 at 12:57 +0100, Anders Darander wrote:
> * Otavio Salvador <otavio@ossystems.com.br> [111221 12:37]:
> > On Wed, Dec 21, 2011 at 09:11, Richard Purdie <
> > richard.purdie@linuxfoundation.org> wrote:
>
> > If we change nativesdk to become a prefix, the problem can share the
> > same code as multilib and become much more widely usable rather than the
> > current special cases. Its obviously a fairly major change in recipe
> > naming though. Would changing this be acceptable?
>
> > I second this as this makes it more consistent and predictable (with the plus
> > of avoiding naming hacks too).
>
> I think I'll second this as well...
>
> So far, I haven't used the multilib-features, but just to be sure, there
> is no problem with using prefixes both for multilibs and nativesdk?
> (Like I said, I haven't studied the multilib code/usecases, thus it's
> quite possible that this is a non-issue).
No, assuming the namespaces are kept separate which isn't an issue as
long as you never want a multilib called "nativesdk" :)
Cheers,
Richard
next prev parent reply other threads:[~2011-12-21 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 11:11 RFC: nativesdk and native recipe names Richard Purdie
2011-12-21 11:37 ` Otavio Salvador
2011-12-21 11:57 ` Anders Darander
2011-12-21 12:59 ` Richard Purdie [this message]
2011-12-21 11:55 ` Phil Blundell
2011-12-21 12:58 ` Richard Purdie
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=1324472399.16323.26.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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.