Take the 2-minute tour ×  I have several (bash) scripts that are
run both individually and in sequence. Let's call them one, two,
and three. They take awhile to run, so since we frequently run
them in order, I'm writing a wrapper script to simply call them
in order.  I'm not running into any problems, per se, but I'm
realizing how brittle this is. For example:  script two has a -e
argument for the user to specify an email address to send errors
to. script three has a -t argument for the same thing. script
one's -e argument means something else  My wrapper script
basically parses the union of all the arguments of the three
subscripts, and "does the right thing." (i.e. it has its own
args - say -e for email, and it passes its value to the -e arg
to the second script but to the -t arg for the third).  My
problem is that these scripts are now so tightly coupled - for
example, someone comes along, looks at scripts two and three,
and says "oh, we should use the same argument for email
address", and changes the -t t