Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ship conda package metadata with matplotlib? #3311

Closed
dmcdougall opened this issue Jul 26, 2014 · 8 comments
Closed

Ship conda package metadata with matplotlib? #3311

dmcdougall opened this issue Jul 26, 2014 · 8 comments

Comments

@dmcdougall
Copy link
Member

@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
Copy link

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

@tacaswell tacaswell added this to the v1.4.x milestone Jul 27, 2014
@tacaswell
Copy link
Member

@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
Copy link
Member

mdboom commented 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
Copy link
Contributor

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

@asmeurer
Copy link

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
Copy link
Member

Not willing to block 1.4.1 on this issue, re-mile stoning to 1.4.x

@pelson
Copy link
Member

pelson commented 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.

@pelson pelson closed this as completed Oct 7, 2014
@anntzer
Copy link
Contributor

anntzer commented Jul 12, 2018

xref discussion starting at #9773 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants