Closed ktran9891 closed 5 years ago
We have a lot of shell scripts lying in various folders. "Real" software would have users simply call these scripts via command line, like gaspy update_db instead of cd /path/to/GASpy/scripts; ./update_db.sh.
gaspy update_db
cd /path/to/GASpy/scripts; ./update_db.sh
As per our discussion, we can simply add a leading gaspy_* to each script and then the appropriate /bins PATH
gaspy_*
/bins
PATH
If we've ignored this issue for this long, then we probably don't need to do it.
We have a lot of shell scripts lying in various folders. "Real" software would have users simply call these scripts via command line, like
gaspy update_db
instead ofcd /path/to/GASpy/scripts; ./update_db.sh
.