From: Bernard Li on Thursday, April 28, 2005 10:06 AM > >Hey guys: > >> I'd also like to see the "./install_cluster" only needed the >> first time. >> That could be done explicitly via your new "make install" (or >> "./configure"?) or implicitly via "oscar_wizard" (which, >> given our usage, should just be "oscar"). > >For the last little while, I have been using ./install_cluster only for >the first time. After the initial run was successful, all I do to >invoke the wizard is run 'cd scripts; ./oscar_wizard'.
We just need to: 1) Make sure the wizard starts iff it appears the required infrastructure is present or make it responsible for installing that stuff. BTW, we now install a lot of stuff way before actually needed--taking a long time to get the wizard up. I'd like to explore installing things like SIS on-the-fly, i.e., when the bits are actually needed by the wizard. A proper set of per-step prerequisites would solve a lot of new-distro problems, e.g., like the ones I repeatedly tripped over with MDK. I've been contemplating something that captured the "use" statements, either pre-parsing or just looking for error messages. 2) put the wizard, or a link, into /opt/oscar or on the PATH somewhere. -- David N. Lombard My comments represent my opinions, not those of Intel Corporation. ------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id5hix _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
