Repository navigation
Ship conda package metadata with matplotlib? #3311
Description
@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?
Activity
asmeurer commentedon Jul 26, 2014
The thing I'd like to see more package maintainers do is ship and maintain their own conda recipes.
tacaswell commentedon Jul 27, 2014
@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 commentedon Jul 27, 2014
I've been working on this a bit over here, but it's not done yet: conda-archive/conda-recipes#144
jankatins commentedon Jul 29, 2014
@asmeurer: is there any "best practise" document for package maintainer? I would be happy to add this to yhat/ggplot.
asmeurer commentedon Jul 29, 2014
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_").
tacaswell commentedon Sep 30, 2014
Not willing to block 1.4.1 on this issue, re-mile stoning to 1.4.x
pelson commentedon Oct 7, 2014
I'd say let's close it. @asmeurer - if you do develop a best practice, or want a large project to try your ideas out on, let us know and we can add the necessary
yaml.anntzer commentedon Jul 12, 2018
xref discussion starting at #9773 (comment).