BUILD.md in instrumental_tools-1.1.3 vs BUILD.md in instrumental_tools-1.1.4

@@ -16,10 +16,16 @@
 
 to push a new copy of the gem directly to RubyGems. This presumes you have the correct `rubygems_api_key` available in your system Gem config.
 
 ## `deb`, `rpm` and `tgz` packages
 
+To build everything, use the following command:
+
+```
+rake package
+```
+
 Building new `deb`, `rpm` and `tgz` packages can be done via the following rake commands:
 
 For 32 bit Linux:
 
 ```
@@ -32,20 +38,32 @@
 ```
 rake package:linux-x86_64:package
 rake package:linux-x86_64:tarball
 ```
 
-
 For Mac OS X:
 
 ```
 rake package:osx:tarball
 ```
 
 `deb` and `rpm` packages should be pushed to PackageCloud. You will need to ensure you have the `package_cloud` gem installed (`bundle install` should install it for you - see the [PackageCloud instructions](https://packagecloud.io/docs#cli_install) otherwise). You will also need write credentials to PackageCloud available in `~/.packagecloud`; they will follow the format:
 
 ```
 {"url":"https://packagecloud.io","token":"YOUR PACKAGECLOUD API TOKEN"}
+```
+
+You will need to install some things:
+
+```
+brew install gnu-tar --with-default-names
+brew install rpm
+```
+
+And then use the package_cloud gem to push our packages.  For example:
+
+```
+package_cloud push expectedbehavior/instrumental/ubuntu/precise instrumental-tools_YOUR_VERSION_HERE_amd64.deb
 ```
 
 On release, the tarball should be uploaded to the Github releases page and linked to from the main README.md.
 
 ## `exe` packages