Add airflow 1.8.0 recipe to conda-forge.

[sodre]

The recipe currently does not build pass the test because

• flask-swagger
• python-nvd3
  • update python-slugify-feedstock
• dependency on flask-login =0.2.11 (Request flask-login 0.2.11 flask-login-feedstock#5, Create build of 0.2.11 version flask-login-feedstock#6)
• dependency on gunicorn >=19.3.0,<19.4.0 (Request gunicorn 19.3.0 gunicorn-feedstock#6)
• dependency on flask-admin =1.4.1 (Flask-admin 1.4.1 flask-admin-feedstock#3)
• Decision from @conda-forge/core on how to handle the extra features/requirements.

I will be working to create additional packages for those.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/airflow) and found it was in an excellent condition.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/airflow, recipes/flask-swagger, recipes/python-nvd3, recipes/python-slugify) and found it was in an excellent condition.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/airflow, recipes/flask-swagger, recipes/python-nvd3) and found it was in an excellent condition.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/airflow, recipes/flask-swagger) and found it was in an excellent condition.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/airflow) and found it was in an excellent condition.

[sodre]

@conda-forge/core,
I need some input on how to handle the extra_requires for airflow. It is not a small-list so I don't think adding all of them to the recipe is the best choice. I know CIO is working on the establishing the "optional" requirements but while that does not arrive what have we done lately.

One possibility is to create several airflow- metapackages that brings in the additional dependencies. Is there a conda-forge example for that?

[mariusvniekerk]

So for now i would try and get a minimal airflow recipe building fully on conda-forge.

Treating the additional dependencies as metapackages for now is probably the simplest approach. For a few of those sets of dependencies you are going to have to submit additional conda-forge packages in any case so it may be simpler for you to iterate that way?

[jakirkham]

Have heard conda 4.4 has support for optional dependencies, but do not know how one would take advantage of this. Maybe ask at conda or conda-build how to use this.

[sodre]

In the short term I will go with @mariusvniekerk suggestion of a minimal airflow install. I will create an issue for the missing extra-packages for airflow and slowly create the associated metapackages.

The new feature in for handling optional dependencies in conda through meta.yaml is solved through conda/conda-build#2001. Once it becomes part of conda-forge we can augment the main recipe.

[sodre]

@conda-forge/core this is ready for review.

[pmlandwehr]

Congrats!

[sodre]

I need to start getting the add-ons done, or just wait for conda 4.4.