> > about prefixing all oscar defined commandas by "o_". > > > > For instance "opd" -> "o_package_downloader" > > "install_cluster" - > "o_install_cluster" > > ... > > I'd prefer "oscar_". Especially since we decided at IU that > "install_cluster" will go away, in favor of a top-level "oscar" command. > So you invoke "oscar" to install your cluster, and [eventually] also > invoke "oscar" to get into maintenance mode.
OK. Long names are cool (because they are explicit) especially when you don't have to type them (automatic completion). opd -> oscar_package_downloader ... You propose install_cluster -> oscar I think that if we want to separate maintenance and installation we should use something like : oscar_install_cluster oscar_maintenance_tool Because in the middle of "oscar_" commands, havind an "oscar" one will not be clear... Ben -- Benoit des Ligneris Etudiant au Doctorat -- Ph. D. Student Web : http://benoit.des.ligneris.net/ Mydynaweb Developpe(u)r: http://mydynaweb.net/ Centre de Calcul Scientifique http://ccs.USherbrooke.ca/ OSCAR Symposium-May 11-14 http://oscar2003.ccs.USherbrooke.ca/ ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
