On Tue, Jun 06, 2006 at 10:42:43PM -0700, Bernard Li wrote: > Hi Ted: > > I believe that if you re-install OSCAR with the latest revision
It was my impression that it was supposed to be ok to run start_over before doing so. Since the previous revision I had (r4871) had a start_over script with a syntax error, there was no evident reason why I should not run the new (r4969) one rather than fixing the old one. > it will generate the "pre-oscar rpmlist" during installation, therefore > before you run "start_over" you should always have this list. Unless something has gone wrong, necessitating starting over. > From the sounds of it, we should simply bail if the pre-oscar rpmlist does > not exist since this should not be a situation we want to be in. Bailing out is in fact the (ungraceful) result of the current behaviour. According to a note I made from one of the lists, "when rerunning wizard, may want to rm -rf $OSCAR_HOME/tmp". That's the directory where pre-oscar.rpmlist lives. If the presence of pre-oscar.rpmlist is going to be essential to the functioning of start_over, perhaps it shouldn't be in $OSCAR_HOME/tmp. What harm is there in start_over doing the best it can (with a warning message), especially as the code to do so is mostly in place? Note also that a missing pre-oscar.rpmlist is not the only possible reason for yum not to have anything to remove. Whether or not it's considered appropriate for start_over to refuse to function in the absence of pre-oscar.rpmlist, start_over should still avoid invoking invalid command lines. -- Ted Powell <[EMAIL PROTECTED]> http://psg.com/~ted/ "If you don't look, you don't know." Dr. Sam Ting, Nobel laureate experimental physicist. _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
