On Tue, Apr 03, 2012 at 09:32:27AM -0700, Darren Hart wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 04/03/2012 09:25 AM, Martin Jansa wrote: > > On Tue, Apr 03, 2012 at 09:01:01AM -0700, Darren Hart wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- Clear reproducible testing > >> results. Whether or not a pair of git clones and some tinkering > >> can result in the same thing as a poky repository or not isn't > >> relevant in my opinion. I believe that we need a consistent mode > >> of validating support for a Yocto Project X.Y release. Now if > >> that is accomplished by building with the poky repository of the > >> same vintage or by running some script that pulls the right bits > >> together independently.... I honestly don't care, but I do think > >> it should be consistent. > > > > 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, but by > > checkouting upstream repositories or using submodules or whatever. > > > > That's what oebb.sh and SHR makefile does for master/shr HEADs, but > > can be extended do it for particular version too. > > > This is certainly doable, but it doesn't address the stabilization > buffer poky provides that I mentioned.
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 independent of this effort (gcc, eglibc, make) but we're talking about oe-core and bitbake. The folks in charge of poky the repo are in charge of oe-core and bitbake. There might be an unintentional lag between when Richard can push changes to poky the repo, but I don't think it's great (and hey, freeing up Richard's time for other stuff is probably a good thing :)). -- Tom
signature.asc
Description: Digital signature
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
