Hi all, I am almost done with the cleaning-up of the bootstrap mechanism (in trunk). This mechanism is not yet directly used when executing ./install_cluster because few small details still need to be addressed (more testing and documentation).
Note that this modification also introduces a configuration file for OSCAR (based on Jean's remarks), to slowly move to a situation where eveything does not have to be installed in $(OSCAR_HOME), i.e., the capability to install OSCAR directly into the system. This configuration file is currently $(OSCAR_HOME)/share/oscar.conf (but can also be installed in /etc/oscar/), AppConfig is currently used to parse this configuration file and therefore AppConfig has been introduced as a prereq. The configuration of this prereq has to be updated for all Linux distributions other than Debian. Also note that my modifications include a simple mechanism to parse this configuration file and get information (see $(OSCAR_HOME)/lib/OSCAR/ConfigManager.pm); i will give more details about that later. Back to the bootstrap mechanism, if you want to use it please execute "./scripts/oscar-config --bootstrap"; it should fully initialize OSCAR. Typically it does the following: - install AppConfig in order to parse the configuration file (this is a new prereqs, the configuration file has to be updated for Linux distributions other than Debian), - install prereqs for smart binary packages installation, - install base prereqs, - install other prereqs based on the ./share/prereqs/prereqs.order, - init the database, - init server side core packages. For each of these steps, we first check the current status. For instance, it means that if a prereq is already installed, we do not try to install it again. This is done to implement later two modes (as requested by some other developers): one mode were prereqs and configuration details are checked and automatically install/setup if not already done; one mode where we display problems to the user, the user being in charge of applying the appropriate manually fixes. The later mode is not yet implemented, currently eveything is done automatically. In summarize, if you execute "./scripts/oscar-config --bootstrap", you should be able to use directly the GUI and the CLI. That will also allow me to move on for the implementation of the new GUI. Finally, note that the code is not yet perfect (for instance source comments and documentation are still missing) but i wanted to check-in my code before the holidays break just in case other developers want to test it. :-) Let me know if you have any problems or if you have any questions. Regards, Geoff ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
