updates to README to reflect new build system

README.md

@@ -38,12 +38,14 @@ prerequisites are assumed:
   recommended.
 - [`docker`](https://www.docker.com/)
 - [`git`](https://git-scm.com/)
+- [`bioconda-utils](https://github.com/bioconda/bioconda-utils)
 
 ### Step 1: Create a new recipe
 
 Fork this repository or create a new branch to work in. Within the new branch,
 [create a recipe](http://conda.pydata.org/docs/building/build.html)
-(`your_package` in this example) in the `recipes` directory. See our [guidelines](GUIDELINES.md) for best practices and examples.
+(`your_package` in this example) in the `recipes` directory. See our
+[guidelines](GUIDELINES.md) for best practices and examples.
 
 ### Step 2: Test the recipe
 
@@ -58,19 +60,22 @@ Bioconductor packages will be built using:
 
     conda build recipes/your_package --channel bioconda --channel r
 
-Then, you can test it in the docker container with:
+Then, you can test it using the `bioconda-utils` tools. This should work
+whether on OSX or Linux:
 
-    docker run -v `pwd`:/bioconda-recipes bioconda/bioconda-builder --packages your_package --env-matrix /bioconda-recipes/scripts/env_matrix.yml
+    bioconda-utils build recipes config.yml --package your_package
 
-To optionally build for a specific Python version, provide the `CONDA_PY`
-environmental variable. For example, to build specifically for Python 3.4:
+Adding the `--docker` flag will build your package using a CentOS 5 Docker
+container to maximize compatibility. This will automatically export your conda
+build directory to the container, so that any packages you build will be
+accessible to your machine even when not running in a Docker container:
 
-    docker run -e CONDA_PY=34 -v `pwd`:/bioconda-recipes bioconda/bioconda-builder --packages your_package --env-matrix /bioconda-recipes/scripts/env_matrix.yml
+    bioconda-utils build recipes config.yml --package your_package --docker
 
 To optionally build and test all packages (if they don't already exist), leave off the
 package name:
 
-    docker run -v `pwd`:/tmp/conda-recipes bioconda/bioconda-builder --env-matrix /bioconda-recipes/scripts/env_matrix.yml
+    bioconda-utils build recipes config.yml --docker
 
 If rebuilding a previously-built package and the version number hasn't changed,
 be sure to increment the build number in `meta.yaml` (the default build number
@@ -113,9 +118,11 @@ For other styles, replace ``?style=flat-square`` with ``?style=flat`` or
 
 ### Building packages for Mac OSX
 **By default, recipes will be built for both Linux and OSX**
-(see "The bioconda build system" section below) upon submitting
-a pull request. Many recipes build cleanly on Linux but not on OSX. The easy
-fix is to explicitly skip the OSX build using a [platform-specific
+(see "The bioconda build system" section below) upon submitting a pull request.
+Many recipes build cleanly on Linux but not on OSX. The easiest way to find out
+is to let the travis-ci tests try building for both platforms. If it fails on
+OSX but not Linux, the easy fix is to explicitly skip the OSX build using
+a [platform-specific
 selector](http://conda.pydata.org/docs/building/meta-yaml.html#skipping-builds)
 on a line in the `meta.yaml` that skips the build, like this:
 
@@ -141,7 +148,7 @@ To test all OSX recipes (skipping those that define `skip: True #[osx]`) use
 the following from the top-level dir:
 
 ```bash
-scripts/build-packages.py --repository . --env-matrix scripts/env_matrix.yml
+bioconda-utils build recipes config.yml
 ```
 
 ### Managing multiple versions of a package
@@ -164,25 +171,16 @@ updated when new releases are made.
 
 ### Other notes
 
-We use a pre-built CentOS 5 image with compilers installed as part of the
-standard build. To build this yourself, you can do:
+We use the docker container `continuumio/conda_builder_linux` pre-built CentOS
+5 image with compilers installed as part of the standard build. To debug
+a recipe in this container, run it in interactive mode while exporting the
+recipes directory to the `/home/dev/recipes` dir in the container:
 
-```bash
-docker login
-(cd scripts && docker build -t bioconda/bioconda-builder .)
-```
-
-Then test a recipe with:
 
 ```bash
-docker run -v `pwd`:/bioconda-recipes bioconda/bioconda-builder --packages your_package
+docker run -it --rm -v `pwd`/recipes:/home/dev/recipes continuumio/conda_builder_linux /bin/bash /opt/share/internal_startup.sh
 ```
 
-If you wish the open a bash shell in the Docker container for manual debugging:
-
-```bash
-docker run -i -t --entrypoint /bin/bash bioconda/bioconda-builder
-```
 
 ## The bioconda build system
 This repository is set up on [Travis CI](https://travis-ci.org) such that on