Ship conda package metadata with matplotlib?

[dmcdougall]

@asmeurer In your talk at SciPy 2014, you mentioned this helps the conda developers. Perhaps you can weigh in with pointing out what files the matplotlib repo needs to eat?

[asmeurer]

The thing I'd like to see more package maintainers do is ship and maintain their own conda recipes.

[tacaswell]

@asmeurer I don't think we have any local conda expertise. If you can get us something in the next week or so we can probably get it shipped with 1.4.0.

[mdboom]

I've been working on this a bit over here, but it's not done yet: conda-archive/conda-recipes#144

[jankatins]

@asmeurer: is there any "best practise" document for package maintainer? I would be happy to add this to yhat/ggplot.

[asmeurer]

Not presently. We are still working out what the best practices would be. If you are a package maintainer, your conda recipe theoretically is quite simple, because you don't need to do things like patch the source or do any hacks in the build script. You can just fix any issues that come up directly.

We do have some new environment variables that are helpful if your package is in git (search http://conda.pydata.org/docs/build.html for "GIT_").