On 06/10/2014 10:31 AM, Marlon Smith wrote: > Hi everyone, > > We've decided to use Yocto in our company's product! And I have a > question: > > Since Yocto is updated pretty frequently, at some point we'll need to > freeze everything and keep a permanent copy so that we can make small > changes/bug fixes without having to worry about anything being changed > outside of our control. My current theory is that we'll do a bitbake -c > fetchall, then zip up the entire Yocto directory and save it somewhere > so we'll always have a static copy. We'll place our application and > custom bsp layer under a separate Git repository, and then to do a build > we'll just combine everything together and run bitbake on the whole > thing. > > Is there a better or recommended way of doing this?
This is how I provide a stable base for people doing SDR work with OE. https://github.com/balister/oe-gnuradio-manifest/tree/daisy I'm sure you'll get several other suggestions also. Pick what works best for your team. Philip > > Thanks again, and I'm excited to start working with Yocto! > > Marlon > > > -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
