On 11/1/07, NZG <[EMAIL PROTECTED]> wrote: > Is there a simple way to "freeze" a build? > We're having a lot problems keeping our OE version buildable due to websites > going down, broken links, and git updates that force us to upgrade. > > Once we get all the software downloaded and working, we want OE to lock into a > static set of sources that are accessable to all our engineers and customers.
You need to lock your BB and mtn tree, I do this by simple fixing the version in the scripts that checkout the BB and OE trees. I suppose you could also maintain your own mtn branch, etc. > I suppose we could copy the source directory to a local network location and > update all the packages to point to this ftp/http source, but to my knowledge > that would involve manually editing every single package. I think bitbake will look at CVS_TARBALL_STASH as a download source, so you can probably put your local downloads directory behind a web server, and then point CVS_TARBALL_STASH to it ... Looking at the bitbake source, it looks like SRC_TARBALL_STASH, and CVS_TARBALL_STASH do the same thing, so we should probably update the local.conf.sample to SRC_TARBALL_STASH as it should apply to all the fetchers -- not just cvs. Cliff -- ======================= Cliff Brake http://bec-systems.com _______________________________________________ Openembedded-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
