Applied and pushed to yocto-docs/master. Thanks Robert. Scott

This rather narrow answer is only useful if you are running a MatchBox desktop. There are many other deployment scenarios which would require a different approach.

Signed-off-by: Robert P. J. Day <rpjday@...> --- diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index 8a0e9a4..ef7d88c 100644 ---

Hi Autif, thanks a lot for providing the answer here. Since no one is showing any objections here, I updated the wiki page with your answer

Experience survey of using Yocto 1.2 Q: Which architecture did you choose to build? A: qemux86 and beagleboard Q: How easily were you able to build an image and boot an image? A: This may be a

I'd really like to see this as well. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

Merged into meta-qt3 Thanks Sau!

I like what Chris said. I vote for this. It is standard SCM practice. All development goes on in a branch. Integration on another branch. When good enough, it is merged to master and tagged as a

I really don't see what the issue is here. If you want a stable branch, we can look into creating such a thing upstream, though I'm personally of the opinion that master should remain

I really think what you're calling a stabilization buffer is what others of us see when we branch the repo(s) we're working on until we're happy with the changes. -- Tom

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I expect the buffer to be empty at times. Hopefully *MOST* of the time. - -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I believe there is. It's a small temporal buffer though. I'd be interested in RP's thoughts here. - -- Darren Hart Intel Open Source Technology

And is it? OE @ ~ $ diff -rq openembedded-core/ projects/poky/ | grep -v '\.git' Files openembedded-core/README and projects/poky/README differ Only in projects/poky/: README.hardware Only in

While I want to reply to your whole email, I want to ask now, is there really a stabilization buffer being provided? I could see that being the case if we were talking about depending on something

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is certainly doable, but it doesn't address the stabilization buffer poky provides that I mentioned. - -- Darren Hart Intel Open Source

Attendees: Beth, Paul, Mark, Saul, Joshua, Chiu-pi Schih (InteL), ScottR, Jeff, Michael, Song   This week's focus: Bug fixing especially HOB/build appliance issues, core build system bugs.

so teach setup script something like: poky.sh checkout X.Y (which checkouts whatever parts are needed for X.Y) poky.sh update X.Y (dtto) Which creates the same structure like poky repository has,

It's more similar to fakeroot than sudo. pseudo and fakeroot don't actually perform operations as root, they just make programs running under them think that they are (for purposes of e.g. getting

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Tom, That's been stated by RP himself and think we're all agreed on it. That has been suggested and it has some merit as a deployment mechanism. I

ah, i think i might have done this under oe-core, that would explain it. rday -- ======================================================================== Robert P. J. Day