> > /usr/bin/geda could be a simple shell script that parses command line > arguments and calls the right tool(s) on the old name. This way existing > makefiles and user habits wouldn't break while we could have a general > geda command. > > > > You can also add addition options in the script - such as a help command that will display all existing programs/scripts tied to gEDA. The "geda-" prefix would be easier in the sense that a shell script could be replaced with symbolic links and allow the user to TAB a few times to see what's available. On the other hand, a script could provide a solid base for more advanced capabilities later on. Also, some structured naming convention would provide a start for people who might contribute scripts to the project - some set of guidelines, if this doesn't already exist.
Ryan _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
