yocto@lists.yoctoproject.org

Re: [meta-qt3] [PATCH 0/1] Qt3 rebuild fix

Merged into meta-qt3 Thanks Sau!

By Saul Wold <sgw@...> · #5770 ·

Re: Moving angstrom under the yocto banner

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

By Brian Hutchinson <b.hutchman@...> · #5769 ·

Re: Moving angstrom under the yocto banner

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

By Chris Larson <clarson@...> · #5768 ·

Re: Moving angstrom under the yocto banner

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

By Tom Rini · #5767 ·

Re: Moving angstrom under the yocto banner

-----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

By Darren Hart <dvhart@...> · #5766 ·

Re: Moving angstrom under the yocto banner

-----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

By Darren Hart <dvhart@...> · #5765 ·

Re: Moving angstrom under the yocto banner

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

By Martin Jansa · #5764 ·

Re: Moving angstrom under the yocto banner

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

By Tom Rini · #5763 ·

Re: Moving angstrom under the yocto banner

-----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

By Darren Hart <dvhart@...> · #5762 ·

Minutes: Yocto Project Technical Team Meeting - Tuesday, April 03, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

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.

By Liu, Song <song.liu@...> · #5761 ·

Re: Moving angstrom under the yocto banner

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,

By Martin Jansa · #5760 ·

Re: Failure expanding variable OE_FEATURES - Poky-1.2_M2.final

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

By Paul Eggleton · #5759 ·

Re: Moving angstrom under the yocto banner

-----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

By Darren Hart <dvhart@...> · #5758 ·

Re: ref manual, ch 5, claims that toolchain should be installed under /opt/poky

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

By Robert P. J. Day · #5757 ·

Re: Failure expanding variable OE_FEATURES - Poky-1.2_M2.final

Hi Chiu-Pi, The M2 release is a Milestone release, which should be suitable for testing. Pseudo is a tool that we use that does similar workas sudo, but keeps better track of the state of files

By Saul Wold <sgw@...> · #5756 ·

Re: ref manual, ch 5, claims that toolchain should be installed under /opt/poky

According to Jessica, there has been no change in the behavior of how the toolchain unpacks. /opt/poky is still used. Scott

By Rifenbark, Scott M <scott.m.rifenbark@...> · #5755 ·

[meta-qt3] [PATCH 1/1] qt-x11-free: fix build failure in do_configure

This line appears to be superfluous and was failing if Makefile did not exist. Signed-off-by: Paul Eggleton <paul.eggleton@...> --- recipes-qt3/qt3/qt-x11-free-common.inc | 3 +-- 1

By Paul Eggleton · #5753 ·

[meta-qt3] [PATCH 0/1] Qt3 rebuild fix

The following change since commit a1c72ecf80c0ded21709aa667c41d65399e4439f: qt-x11-free: fix QA errors (2012-03-14 17:35:09 +0000) are available in the git repository at:

By Paul Eggleton · #5752 ·

1.2 Pre-Release survey

As requested. Q: Which architecture did you choose to build? A: qemuarm, qemumips Q: How easily were you able to build an image and boot an image? A: Easy Q: Is there any surprise to you in the

By Gary Thomas · #5751 ·

Re: ref manual, ch 5, claims that toolchain should be installed under /opt/poky

Robert P. J. Day wrote on 2012-03-26: Did you include the meta-yocto layer when you bake the meta-toolchain? "/opt/poky" is the default settings for the toolchain generated using meta-yocto layer,

By Lu, Lianhao <lianhao.lu@...> · #5750 ·

Messages