I have a quick question. It looks like the kanso distribution is not
idiomatic Node.js. It looks like we clone a repository and run make
(which fetches Git submodules). I thought it might be as easy as `npm -
g install kanso`.
Is it just for historical reasons that you avoided NPM for this
release, or some fundamental incompatibility I didn't notice?
If the former, then would you accept a pull request with tighter NPM
integration? I'm thinking a couple of goals:
* Fix problem with `parser` in Node v0.6
* From a checkout, able to run `npm link` and get a kanso install,
symlinked to the Git repo
* From a GitHub .zip download, able to run `npm install` and get a
kanso install, copied from the Git repo
* Some Make target that preps Kanso for publishing. (Some people have
private NPM archives, but the main user here is Caolan.)
* By running `npm -g install kanso`, people get the `kanso` command in
their $PATH, the latest stable release, etc.
On Dec 5, 3:46 pm, Caolan McMahon <caolan.mcma...@gmail.com> wrote:
> === Cross-posted to the CouchApp group ===
>
> Hi, all,
>
> Today I'm excited to announce a new release and _change of direction_ for
> the Kanso project.
>
> Kanso is now a generic build-system for CouchApps and completely framework
> agnostic. It even supports multiple styles, including reupholster and
> node.couchapp.js (support for the Python tool is experimental).
>
> The Kanso team has been developing some great tools for managing and
> creating CouchApps, and now we're able to share these resources with the
> whole CouchApp community! These libraries and tools are built by people
> working with CouchApps every day in real-world projects and represent
> months of hard work.
>
> The new website is available athttp://kan.so
> there are a lot!). You can see the work so far athttp://kan.so/docs.
To be honest I found it a bit of a pain maintaining an npm package for
Kanso as well as supporting make. Though, your post is persuading me
that we should look into reviving npm support ;) At the time I didn't
want to add another dependency in the form of npm, so the makefile had
to be an option. Now, it seems newer releases of node come with npm
included, so potentially we could rely on it (once node v0.6.x is
fixed for Kanso).
The goals you defined sound great, this would get us closer to having
nice tarball releases on the website too. I'd be very happy to accept
a pull request towards these goals, so let me know if you need any
help.