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

Prepare conda installation #156

Open
pgierz opened this issue Oct 4, 2021 · 6 comments
Open

Prepare conda installation #156

pgierz opened this issue Oct 4, 2021 · 6 comments

Comments

@pgierz
Copy link
Member

pgierz commented Oct 4, 2021

Hope to fix conda installation on the way, currently it seems to be totally broken.

Paul: I can have a look at this, would you be opposed to modifying the CI so that it makes automatic conda publication on any tag push? I had recently been playing around with that for one of my private projects.

@pgierz pgierz changed the title #### Prepare conda installation. Prepare conda installation Oct 4, 2021
@koldunovn
Copy link
Member

I would love that! Let me know what you need from my side - I think we should make access for you (or CI) to https://github.com/conda-forge/pyfesom2-feedstock ?

@pgierz
Copy link
Member Author

pgierz commented Oct 4, 2021

Maybe we at some point need a robot account ;-) If I could be admin on the feedstock, that should give me everything I need. I might need to get in touch with you if I get stuck, my "publishing" has so far only been with PyPI, so I still need to learn how conda does things. There are already github action templates set up though, so I would as a first attempt just follow those.

@koldunovn
Copy link
Member

koldunovn commented Oct 4, 2021

So then I will not do the release just now, so that you can play around with automatic publishing, and try to merge changes (if there will be any) to daskification branch?

I added you as a maintainer: conda-forge/pyfesom2-feedstock#3
Here are the instructions on how to update the package: https://conda-forge.org/docs/maintainer/updating_pkgs.html

Most important at this stage would be to

  • remove Basemap, that still hangs there for some stupid reason,
  • add new dependencies,
  • make sure the MANIFEST is working (now the geojson folder is not copied during the installation)

@pgierz
Copy link
Member Author

pgierz commented Oct 5, 2021

New dependencies can be detected and added automatically, see #157

@koldunovn
Copy link
Member

@pgierz can we close this?

@pgierz
Copy link
Member Author

pgierz commented Jul 22, 2022

Yes. We can reactivate this if demand rises, but auto-publishing is at the moment just a pipe dream which would be "nice to have". Other things are more important at the moment though

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

No branches or pull requests

2 participants