From: J. L. <vwy...@gm...> - 2010-08-17 17:45:10
|
I honestly think more testing needs to be done before pushing. I have only built an image once successfully since purchasing an overo, and never been able to build a gnome image! As you say Steve OE is complex so I think you being the only tester is a bad practice. We need more people testing and the build machine seems just as dependent as the upstream changes not breaking anything. Also Steve if you read what the guys on the OE list said about the same question posed there. We are a random branch according to them. I also dont really see much activity for fixes coming from you let alone anyone that gets put to the OE dev branch. Also you just being able to build the basic image is not enough testing in my book. You should have a test image that builds as many different programs and configurations as possible (hence why more testers and people helping you are needed). As some programs build at certain times and others dont. There seems to be no consistency at all and not very many having exactly the same issues once a break occurs. You need help Steve you being a one man part time person is not enough support or people working to better the overo tree. Why does gumstix only have you doing this? Why are there not more people from gumstix themselves helping you and making the overo tree as great as it can and SHOULD be. I would gladly volunteer time and efforts as I have a few different build machine configurations I could do at home. On Tue, Aug 17, 2010 at 10:08 AM, Steve Sakoman <sa...@gm...> wrote: > On Tue, Aug 17, 2010 at 8:51 AM, AJ ONeal <coo...@gm...> wrote: > >> How about something like this: >> All updates are done in the "moving-target" (unstable) branch > > That is the org.openembedded.dev branch. > >> Any time the "moving-target" branch will build a clean omap3-desktop-image >> without errors it is merged with the "just-works" (stable) branch > > That is the overo branch. I merge with the upstream > org.openembedded.dev branch approximately once a week. (this info is > on the gumstix.net site IIRC) > > I then do builds of all of the "omap3" images and the > sakoman-gnome-image on my dev machine (Ubuntu 10.04 quad core). I fix > anything that might be broken and then do automated builds of the same > images for both Beagle and Overeo on the www.sakoman.com machine > (Ubuntu 9.04 64 bit server dual core). If successful then the result > is pushed to overo branch. > > In theory that should yield a "just works" branch. > > In practice people still have problems. OE is a *very* complex build > environment that still has dependencies on the package set installed > on the build machine as well as lingering dependency issues that show > up randomly depending on the number of cores on your machine and your > settings for PARALLEL_MAKE and BB_NUMBER_THREADS. That is why -c > clean and rebuilds of failing packages more often than not result in a > good build the second time around. > > If you find fixes for the above, by all means submit the patches to > the OE mailing list! You will have many grateful users :-) > >> The "just works" branch. >> Then try to do a "bitbake world" on the "just-works" branches and tag that >> branch as special (or merge it with a "no-really-it-does-work" branch). > > Again, nice in theory. But I have *never* seen a 'bitbake world' > succeed in real life :-) > >> Who is in charge anyway? Is that person interested in making things more >> reliable? Does that person want help? > > I guess I am the one currently "in charge" of the Overo branch. Of > course I would like things to be more reliable! But this is a very > big effort on a moving target, so the more folks that help the better. > I'm one part-time consultant who is also doing board support for > u-boot and the linux kernel so there is only so much that I can > accomplish by myself. > > Again if you find fixes to OE issues, submitting them to the OE > mailing list is the right thing to do. The Overo branch is 99.9% > identical to org.openembedded.dev -- we use a custom linux and u-boot > recipe so that we don't break every time someone upstream changes the > "one size fits all" recipes upstream. We also have custom image > recipes to control what goes in the NAND. If you find issues with > those recipes, the gumstix list is the place to post your patches. > But in my experience, the vast majority of build issues that people > encounter are generic OE issues. Fixes for those should go to the OE > list (and a cc to the gumstix list would be nice). > > Steve > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |