The various automation scripts are dependencies of this bug. Check the dependency tree for the deets.
And now, to add these features to the skynet client. So: it should deal with a local csprocessor.cfg file in the current local directory, and it should use that file with the new commands: skynet refreshlocal skynet updateremote skynet build So when skynet build is invoked with no arguments, it should check for the presence of a csprocessor.cfg file.
*** This bug has been marked as a duplicate of bug 769009 ***