-----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. - -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPeyYbAAoJEKbMaAwKp364OUMH/j8LTjnxSHNS7bc2oDQXmx3r E/HzG2t2Q+u0N7Zg/H/1OHNjmZesDr94GlnqHzVMOQRXdpmnx/BZjLuTCL//R43Y wP3jH/gCrAqdk2EJmqNkNQN3A5iQT8Ybj9dYfd0tr6M+GnN/9MpaL8VyW1Fz3Rxo gHgxNu+mvB8mKT4Ix45a91yV107LQ2enPZ7OHHURLGRdjxF1SCi0owuP/hQzEAYl qdgrc3KeBcrAs9ubC9OyAg68G7N8kvgSNSQRegVcELRa34k5Lr/6uP7pehT0IY4m meA1E3tGafo1iIpdxSHhM6HwzUwKcWf/RzupGcXXUWuHsVgeaElvUW5u0h7Kkkg= =mdcZ -----END PGP SIGNATURE----- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
