----- "Nasa" <[email protected]> wrote: > ----- "Patrick Ohly" <[email protected]> wrote: > > > On Mo, 2010-10-25 at 12:12 +0100, Nasa wrote: > > > I have been somewhat confused on how system upgrading is being > > handled > > > for meego. If I install a base meego system (ie: 1.0) and use > > zypper > > > (dist-upgrade) to keep up with the latest image -- will this work > > or > > > do I need to download and reinstall for each update I want to > test? > > > > It kind of works. But I was told that the upgrade path is not > tested. > > > > Problems that I have encountered myself on Trunk: > > * version numbers go backward as far as rpm's version > > comparison > > algorithm is concerned > > * incomplete conflicts/replaces meta information > > * new packages are required for correct operation of the > > system, > > but do not get installed because nothing depends on them > > > > So your mileage may vary depending on what you follow. Clearly > would > > be > > desirable, though. > > > > -- > > Best Regards, Patrick Ohly > > > > The content of this message is my personal opinion only and > although > > I am an employee of Intel, the statements I make here in no way > > represent Intel's position on the issue, nor am I authorized to > speak > > on behalf of Intel on this matter. > > Thanks Patrick, > > It's good to know that the upgrade path is untested. I will refrain > from > making bug reports based on my upgraded system. >
Follow up question on this (just to make sure I got it straight)... A single image is the only coherent installation. What I am trying to figure out is, if I want to follow development from 1.1 to 1.2, I would have to install the weekly(?) images (which is actually a fresh install) or run the risk of an instable system if I simply upgraded via zypper. I ask, because this would be significantly different than how other projects work and I want to understand how things do work so I don't create bugs due to a faulty install on my end. Nasa _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
