gEDA-dev: geda naming convention

[Steve Meier]

If you want to write a script go right ahead just don't make in
manditory. Else I wil have to make an even more custom version to make
it non-manditory.

Other wise sure as long as you are having fun,

Steve Meier

Ryan wrote:
>> /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
> geda-dev at moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
>
>