All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Merging multimachine.bbclass into the OE.dev core
Date: Mon, 2 Jun 2008 15:53:33 +0200	[thread overview]
Message-ID: <200806021553.33860.mickey@vanille-media.de> (raw)
In-Reply-To: <1212405013.5008.19.camel@dax.rpnet.com>

On Monday 02 June 2008 13:10:13 Richard Purdie wrote:
> On Mon, 2008-06-02 at 11:26 +0100, Richard Purdie wrote:
> > multimachine has been a kind of second class citizen for a long time
> > having been maintained in its own class.  We now have things like sdk
> > generation which implicitly depend on multimachine being used. I can't
> > think of any reason people wouldn't want to use it and it allows extra
> > flexibility without imposing any added limitations.
> >
> > Is it time we merged it into the core classes and made it the default?
> >
> > The one drawback is it will force an effective wipe tmp for anyone who
> > wasn't using it before.
>
> Its been pointed out that some people only use one target and therefore
> don't like the longer paths when they don't need them.
>
> I'd propose adding a singlemachine.bbclass which gives the old behaviour
> although people using that would do so at their own risk from the
> meta-toolchain and sdk.bbclass perspectives.

Yep, very good.

:M:



      reply	other threads:[~2008-06-02 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 10:26 Merging multimachine.bbclass into the OE.dev core Richard Purdie
2008-06-02 10:53 ` Koen Kooi
2008-06-02 11:10 ` Richard Purdie
2008-06-02 13:53   ` Michael 'Mickey' Lauer [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=200806021553.33860.mickey@vanille-media.de \
    --to=mickey@vanille-media.de \
    --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.