-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Adding geeadd to conda-forge #10
Comments
Hi @giswqs Added the yaml file here . Let me know and I can submit a pull request based on any other edits as needed. |
Your Following conda-forge's guidelines, a few edits are needed:
|
Thanks @giswqs https://github.com/samapriya/staged-recipes/tree/master/recipes/geeadd |
It looks good to me. I believe you don't need to specify Python version in meta.yaml. Python versions are already specified in the setup.py of the package, which meta.ymal will inherit from. |
build seems to work in osx and windows but is failing during merge check for Linux. Would you mind taking a look? |
Hey @giswqs |
Great work! Just wait for the conda-forge team to review it. |
You can replace Lines 213-216 with urllib. See my sample functions below.
|
Used urllib method and modified a few lines to get the desired effect. All checks completed for the new version 0.4.4 and conda-forge yaml file was updated to remove git and updated to v0.4.4. This is also better since it reduces dependency on the project. Thanks for the suggestions, closing this for now. |
Excellent! Thank you for your prompt action! |
I plan to incorporate geeadd into the geemap package, making geeadd one of the dependencies. It would be nice to have this package available on conda-forge. Here is the instruction for adding a package to conda-forge. You can create a
meta.yaml
usingconda skeleton pypi geeadd
. Then fork conda-forge/staged-recipes and add a geeadd folder with the meta.yaml and LICENSE to the recipes folder. Submit a pull request and wait for the review and approval. I can help in this regard if needed. Thanks.The text was updated successfully, but these errors were encountered: