> On Sunday, August 28, 2011 1:14 PM Alison Chaiken wrote: >Joel wrote: >> I suggest building against: >> http://repo.meego.com/MeeGo/releases/1.2.0/repos/ >> and then doing a runtime update to get the stuff in >> http://repo.meego.com/MeeGo/updates/1.2.0/repos/ >> >> What are you looking for in later repos? > > If I'm installing some random user program like Thunderbird or > Rhythmbox or Totem, I'll grab a tarball from the project in question's > trunk/stable/latest branch and configure-make-make_install it, which > nearly always works. Calling a branch "stable" if it's not > tremendously stable is a bit confusing, although it's not IVI's fault > if the Core team is doing so. > > Proceeding with 1.2.0 repos, thanks again. > > Alison Chaiken
Recent testing leads me to change my recommendation. Instead of building a new image I suggest using the image already built in the releases/1.2.0/images directory and then do the updates as needed. I believe the images we released in http://repo.meego.com/MeeGo/releases/1.2.0/repos/ are stable and we did quite a bit of testing updating that image with the "updates" in http://repo.meego.com/MeeGo/updates/1.2.0/repos/ What appears to be badly broken right now is building new images even from the same repos used to build the released images. I've seen several different folks reporting various symptoms that all seem to be related to changes in the MIC image tool since May 19. The break appears to have happened around July 26. regards Joel _______________________________________________ MeeGo-ivi mailing list [email protected] http://lists.meego.com/listinfo/meego-ivi
