<commit_before># biocore_recipes
Conda recipes for biocore projects.

# Setting up the build environment

We follow the instructions in the [conda
docs](http://conda.pydata.org/docs/build_tutorials/pkgs.html#tutorial-basic-tutorial-for-building-a-conda-package),
but here's an overview of the process.

Since we have conda already installed, we update it and use it to
install `conda-build`. In linux, we also install `patchelf`

```
$ conda update conda
$ conda install conda-build
$ conda install patchelf
```

# Creating recipes


Most recipes were created using the skeleton command

`conda skeleton pypi pckg`

but they usually require some manual edits (setting requirements
versions, some tests commands...).

To keep them up to date it should be enough to update their
dependencies and version string, but it'd be nice if that was
automatic... They can also be built from git tags or track branches,
but here we're currently building them from PyPI releases (or a master
branch).

# Building packages

First, let's make sure everything is updated when building packages:

```
$ conda update conda conda-build patchelf
```

```
$ conda build qiime
```

If registered in binstar (like PyPI, for conda builds) and logged in
(`$ binstar login`), the build command will give, if successful, a
command to update the binary package. It can be done automatically by
configuring `conda config --set binstar_upload yes`.<commit_msg>DOC: structure README<commit_after># biocore_recipes
Conda recipes for biocore projects.

# Setting up the build environment

We follow the instructions in the [conda
docs](http://conda.pydata.org/docs/build_tutorials/pkgs.html#tutorial-basic-tutorial-for-building-a-conda-package),
but here's an overview of the process.

Since we have conda already installed, we update it and use it to
install `conda-build`. In linux, we also install `patchelf`

```
$ conda update conda
$ conda install conda-build
$ conda install patchelf
```

# Creating recipes


Most recipes were created using the skeleton command

`conda skeleton pypi pckg`

but they usually require some manual edits (setting requirements
versions, some tests commands...).

To keep them up to date it should be enough to update their
dependencies and version string, but it'd be nice if that was
automatic... They can also be built from git tags or track branches,
but here we're currently building them from PyPI releases (or a master
branch).

# Building packages

First, let's make sure everything is updated when building packages:

```
$ conda update conda conda-build patchelf
```

```
$ conda build qiime
```

# Sharing packages

If registered in binstar (like PyPI, for conda builds) and logged in
(`$ binstar login`), the build command will give, if successful, a
command to update the binary package. It can be done automatically by
configuring `conda config --set binstar_upload yes`.
{'fraction_non_alphanumeric': 0.07271468144044321, 'fraction_numerical': 0.0, 'mean_word_length': 4.588007736943907, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7671135', 'n_tokens_mistral': 848, 'n_tokens_neox': 804, 'n_words': 389}