Stephen Mathieson

If the goal is BitBucket support (which I'm in support of, btw) I'd go about it a bit differently. Rather than providing "url" and "version", maybe something like: ``` json...

err, actually, BitBucket raw URLs are `https://{host}/{owner}/{name}/raw/{version}/{source file}`.. we'll have to do this a bit differently :/

This is true. We'd then either need libgit2 or to fetch a tar ball and extract certain files (like installing executables works currently). I'll have to look at `go get`;...

What about: ``` json "dependencies": { "my-friend/my-friends-package": { "url_format": "https://{owner}@bitbucket.org/{owner}/{name}/raw/0.1.0/{file}" } } ``` And let `url_format` default to `https://raw.github.com/{owner}/{name}/{version}/{file}`? This will allow any arbitrary URL format to be specified, thus...

Well, we're not really cloning; we're just fetching the files listed in your package.json's `src`. If we were cloning, we may as well just use git submodules :p

IMO we shouldn't fix what isn't broken. We've been using a public wiki for nearly 10 years and haven't had a _single_ problem with it.

Fortunately if there is a problem, we can easily revert the change(s) and set up an "authors" group. The wiki is just another Git repository 😄 

I like this idea! I don't think we need to separate it into another program. I'm on board with having `clib uninstall` work for bins and libraries.

Doing `clib uninstall user/repo` where `user/repo` is a _library_ (not a _binary_) should: - error if there is no manifest (`{clib,package}.json`) in `$PWD` - remove the `user/foo` reference in the...

Any updates here? It's very discouraging that this issue has been open for over a year without a maintainer acknowledging it.