On 07/22/2013 05:44 PM, James Lal wrote:
>
> In Makefile:
>
> > @@ -1,3 +1,35 @@
> > +.PHONY: help
> > +help:
>
> this is both great and horrible to me in some ways :)
>
> At we at the complexity level now that I could convince you to use 
> python or node to have some kind of ./bin/gelam thing?
>

No and yes.  If anything, the Makefile is getting less complex; there's 
just a lot of different things you could want to do.  But Makefiles are 
inherently ad hoc things that resemble the business end of a wood 
chipper; people don't like to put their hands in there, and for good 
reason.  They're also not idiomatic for node or pure JS projects.

So I'm fine with going with something more standard.  I think I'd prefer 
using "npm build" and "npm test" for those targets.  I don't know how to 
integrate that into the ArbPL stuff, but the default command-line output 
is useful these days, so it's fine if using the ArbPL UI is just an 
advanced thing you can do.

The "install-into-gaia" target goes away once we change to a more 
npm-ized thing anyways, but that's also just invoking a script with node 
anyways, so we can rig that up somehow.  Shell script for stop-gap?  Not 
sure about the fake-servers, but that could also just be a .js file.

For running the fake-servers, maybe we just add a "run-fake-server.js" 
in bin/ or the root of the repo?