A conda-smithy repository for rapidpy.
Shell
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
ci_support MNT: Updated the feedstock for conda-smithy version 2.1.0. Feb 25, 2017
recipe Initial feedstock commit with conda-smithy 2.0.1. Jan 31, 2017
.gitattributes
.gitignore Initial feedstock commit with conda-smithy 2.0.1. Jan 31, 2017
.travis.yml MNT: Updated the feedstock for conda-smithy version 2.1.0. Feb 25, 2017
LICENSE
README.md
appveyor.yml MNT: Updated the feedstock for conda-smithy version 2.1.0. Feb 25, 2017
circle.yml MNT: Updated the feedstock for conda-smithy version 2.1.0. Feb 25, 2017
conda-forge.yml Re-render the feedstock after CI registration. Jan 31, 2017

README.md

About rapidpy

Home: http://github.com/erdc-cm/RAPIDpy

Package license: BSD-3-Clause

Feedstock license: BSD 3-Clause

Summary: A python interface for the RAPID program (rapid-hub.org).

RAPIDpy is a python interface for RAPID that assists to prepare inputs, runs the RAPID program, and provides post-processing utilities. More information about installation and the input parameters for RAPID can be found at http://rapid-hub.org.

Current build status

Linux: Circle CI OSX: TravisCI Windows: AppVeyor

Current release info

Version: Anaconda-Server Badge Downloads: Anaconda-Server Badge

Installing rapidpy

Installing rapidpy from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge

Once the conda-forge channel has been enabled, rapidpy can be installed with:

conda install rapidpy

It is possible to list all of the versions of rapidpy available on your platform with:

conda search rapidpy --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by CircleCI, AppVeyor and TravisCI it is possible to build and upload installable packages to the conda-forge Anaconda-Cloud channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating rapidpy-feedstock

If you would like to improve the rapidpy recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/rapidpy-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

  • If the version of a package is not being increased, please add or increase the build/number.
  • If the version of a package is being increased, please remember to return the build/number back to 0.