differentiate between fig options and fig commands

[tastapod]

fig [options] command [package...]

fig commands are things like update, list[-remote], publish, clean

fig options are things like --include, --append

So you have:

• fig -i cheese/1.1 -i pie/2.3 update

or

• fig -a ham-1.1.tgz publish ham/1.1

[mfoemmel]

I really like this, but it conflicts with the "executable config" syntax we have now e.g. if you use the "command" statement in a config, you can run it like this:

fig mylib/1.2

Or, assuming we had tagging:

fig mylib

Should we convert this to something like:

fig run mylib

?

[tastapod]

I like fig run mylib - it makes it more explicit. It also means you have a check (fig run implies a command statement, so fig can complain if there isn't one).

[clonezone]

It's a bit late to change the command line processing like this, so this is a "won't do".