use npm for install

[ritch]

Since npm is already a dependency I suggest you create this as an npm package. It would change this:

1. Install the Mac development tools (Xcode and friends).
2. Install node.js.
3. If not covered in #2, install npm: curl http://npmjs.org/install.sh | sh
4. Install node-mime: npm install mime
5. Clone the TermKit repository: git clone [email protected]:unconed/TermKit.git --recursive
6. Users of older git versions will need to type: git submodule update --init
7. Run the NodeKit daemon: cd TermKit/Node; node nodekit.js
8. Unzip and run the Mac app in Build/TermKit.zip

Into this:

1. Install the Mac development tools (Xcode and friends).
2. Install node.js.
3. If not covered in #2, install npm: curl http://npmjs.org/install.sh | sh
4. $ npm install termkit

Where number 4 automates 5, 6, 7 and 8.

Just a thought. If you are interested in adding this, I'd be glad to help with #4.

[shazmoh]

+1 for this idea. Not sure if there a specific reason why this can't be done.

[djbe]

I don't think that's the intention, since the final product will be a self containing app...

[ritch]

Well for now, it could be the means of installing for the people who want to use it now. Eventually the packaged app can either make use of this method, or bundle the node modules. Perhaps both? Npm is the simplest way to manage node dependencies, there's no reason to over complicate it.

[kriswill]

or 4. $npm install termkit-dev

to install specifically from cutting edge git, and download package for stable releases. Might I also suggest that running termkit.app also start up the node.js server, and provide a log window.

[kbrock]

setting up a package.json file was working great for me. (Currently working through the recent socket.io 0.7 and git submodule changes)

I got my package.json file from Floby's branch

Is there a reason why the socket.io is a submodule instead of a npm install?