Move to conda-forge

[pradal]

The idea is to move all the recipes to conda-forge.
This will induce major modification in the code:

• Code need to work with non-patched software:
  Each package needs to run natively, with current version of all the dependencies (bison, boost, ...)

[langmm]

Is this something openalea is still interested in doing? If so, I would like to help with this as I am currently having trouble using the openalea.lpy package within a larger conda-forge environment due to package conflicts. I am familiar with the conda-forge process and would just need a general understanding of the dependency order (i.e. which packages should I start with) and the usernames for additional people who would like to be tagged as feedstock managers.

[pradal]

Thank you a lot for this proposal. I am on vacation but I am quite interesting to use conda-forge.
We have a repository of conda recipes: https://github.com/openalea/openalea-recipes

The order of dependencies is define in https://github.com/openalea/openalea-recipes/blob/master/travis.yml

• openalea.deploy
• openalea.sconsx
• openalea.plantgl
• openalea.lpy