On Wed, 22 Jan 2003, Benoit des Ligneris wrote:
> OK. Long names are cool (because they are explicit) especially when you
> don't have to type them (automatic completion).
>
> opd -> oscar_package_downloader
> ...
That does kinda destroy the niceness of "opd" -- it just rolls off the
tounge and the fingers...
How about an alternate solution: just have a module for all the OSCAR
commands. They should all [eventually] get installed to /opt/oscar-X.Y
somewhere, anyway. And only the sysadmin should probably have these
commands in their path.
So have a module and put it in switcher -- the system default is to not
load it, but root (and/or the sysadmin user) can override that and have it
loaded. So things like "opd" and "oscar_foo" are in their path.
Then oscar_ prefixes become less important.
> 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...
Why?
"oscar" is the top-level, nice GUI thingy that does everything for you.
It will even have a command line interface, if you want (bound to
metamenu). But if you want specific things, use the full oscar_foo
command.
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
-------------------------------------------------------
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
