Ubuntu/Debian packaging

Hey folks,

I don't like it when my software doesn't use my system's package manager:

```
ezyang@sabre:~$ npm install -g keybase-installer
npm http GET https://registry.npmjs.org/keybase-installer
npm http 200 https://registry.npmjs.org/keybase-installer
npm http GET https://registry.npmjs.org/keybase-installer/-/keybase-installer-0.1.8.tgz
npm http 200 https://registry.npmjs.org/keybase-installer/-/keybase-installer-0.1.8.tgz
npm ERR! Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! { [Error: EACCES, mkdir '/usr/local/lib/node_modules']
npm ERR! errno: 3,
npm ERR! code: 'EACCES',
npm ERR! path: '/usr/local/lib/node_modules',
npm ERR! fstream_type: 'Directory',
npm ERR! fstream_path: '/usr/local/lib/node_modules/keybase-installer',
npm ERR! fstream_class: 'DirWriter',
npm ERR! fstream_stack:
npm ERR! [ '/usr/lib/nodejs/fstream/lib/writer.js:171:23',
npm ERR! '/usr/lib/nodejs/mkdirp/index.js:51:17',
npm ERR! 'Object.oncomplete (fs.js:107:15)' ] }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Linux 3.11.0-17-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "keybase-installer"
npm ERR! cwd /home/ezyang
npm ERR! node -v v0.10.15
npm ERR! npm -v 1.2.18
npm ERR! path /usr/local/lib/node_modules
npm ERR! fstream_path /usr/local/lib/node_modules/keybase-installer
npm ERR! fstream_type Directory
npm ERR! fstream_class DirWriter
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:171:23
npm ERR! fstream_stack /usr/lib/nodejs/mkdirp/index.js:51:17
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/ezyang/npm-debug.log
npm ERR! not ok code 0
```

Would you guys be interested in a contributed Debian/Ubuntu package for the keybase command line client?

The issue requests a Debian/Ubuntu package for the keybase command line client, but names no files, tests, or packaging entry point. Start by locating the client's current distribution and installation process, then review Debian/Ubuntu packaging requirements and verify that the package installs the CLI through the system package manager.

Written by the indexing model from the issue text.