From: Richard Purdie <rpurdie@linux.intel.com>
To: Esben Haabendal <eha@dev.doredevelopment.dk>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Distro 1.0 Planning minutes
Date: Wed, 10 Nov 2010 18:01:57 +0800 [thread overview]
Message-ID: <1289383317.1272.104.camel@rex> (raw)
In-Reply-To: <87fwv9mrr6.fsf@eha.doredevelopment.dk>
On Wed, 2010-11-10 at 10:50 +0100, Esben Haabendal wrote:
> "Kamble, Nitin A" <nitin.a.kamble@intel.com> writes:
>
> > Dongxiao: sysroot per machine per recipe
>
> Is it possible to elaborate on this topic? What was discussed and what
> was the conclusion?
This is what we discussed in person in Cambridge, the idea of making it
possible to have one sysroot per machine or one sysroot per recipe. Our
intention is to make this work in the next few months.
I pointed you at the existing task based sstate code which should make
this kind of thing relatively straight forward.
Cheers,
Richard
next prev parent reply other threads:[~2010-11-10 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 3:52 Distro 1.0 Planning minutes Kamble, Nitin A
2010-11-10 9:50 ` Esben Haabendal
2010-11-10 10:01 ` Richard Purdie [this message]
2010-11-10 10:52 ` Esben Haabendal
2010-11-10 13:52 ` 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=1289383317.1272.104.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=eha@dev.doredevelopment.dk \
--cc=yocto@yoctoproject.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.