Hi all, I looked at details of the current integration of OS_Detect in OOD (Ram has made a lot of improvements during the summer).
For prereqs, the current version of OOD is based on the modification of wizard_prep. Wizard_prep find the current distrib (thanks to the OS_Detect framework) and based on that execute the correct setup script for prereqs. Therefore, it is "compliant" with the current trunk (using the modified wizard_prep script). For packages, it is a little bit different because packages are not completely up-to-date regarding the OSCAR trunk. I will try to update OOD this week. For other scripts, they are just integrated the OS_Detect framework and close to the OSCAR trunk. To summarize, if we want to use OOD stuff it is possible to integrate the OS_Detect framework for basic scripts (for example install_cluster) and prereqs. What do you think about that? I will be happy to port some OOD stuff in the OSCAR trunk. Just let me know what is the best solution according to you. Thanks, Le Mardi 25 Octobre 2005 19:19, Jeff Squyres a écrit : > My comment: Excellent! > > How portable are the code changes? Can they come over to the main OSCAR > trunk? I would think that 90+% of this stuff is not Debian specific, > and therefore would be a major boon to the trunk. > > Is it anything close to my patches for install_cluster and > generic-setup? (I don't see a generic-setup in here, but I don't > remember when the OOD SVN was made -- was it made before generic-setup > existed?) > > Geoffroy Vallée wrote: > > Hello, > > > > After the discussion during the call yesterday about the integration of > > the OS_Detect framework, I checked what Ram did for OSCAR on Debian (OOD) > > during the Google SoC. > > > > Ram integrated the framework in several parts of OOD. This version > > includes a component for Fedora, Debian, RedHat and OSX; based on the > > initial version of the trunk (created by Jeff and Thomas i guess). > > Modified files to use the OS_Detect framework are: > > * install_cluster > > * share/prereqs/oda/scripts/setup > > * share/prereqs/perl-XML-Simple/scripts/setup > > * share/prereqs/perl-XML-Parser/scripts/setup > > * share/prereqs/packman/scripts/setup > > * share/prereqs/perl-Tk/scripts/setup > > * packages/apitest/scripts/setup > > * packages/c3/scripts/post_server_install > > * packages/ganglia/scripts/post_install > > * packages/mpich/scripts/post_clients > > * packages/mpich/scripts/setup > > * packages/ntpconfig/scripts/post_server_install > > * packages/pvm/scripts/setup > > * packages/sis/scripts/post_server_install > > * packages/torque/scripts/post_server_rpm_install > > * packages/torque/scripts/post_install > > * lib/OSCAR/MAC.pm > > * lib/OSCAR/WizardEnv.pm > > > > According to me, the major problem we may have to use that is for > > prereqs. Ram had modified prereqs setup scripts because they were still > > deeply based on the RPM format and modifications are pretty important. I > > can give more details if needed. In another hand it may be a good > > opportunity to initiate the integration of OOD in OSCAR. :-) > > > > The code is in the SVN repository (soc-oscardebian branch). > > > > Any suggestions? > > > > Thanks -- Geoffroy Vallée, Ph.D. SSI-OSCAR (http://ssi-oscar.irisa.fr/) OSCARonDebian (http://ssi-oscar.irisa.fr/oscarondebian/) ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
