Created
September 10, 2018 18:14
-
-
Save PhilipMay/7bec8e09b45581393a68f3d3d5281d63 to your computer and use it in GitHub Desktop.
Feedback on conda-forge.github.io
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Hi everybody, | |
| my name is Philip and I am new to conda-force. | |
| At the moment I am maintaining the hyperopt package. | |
| @jakirkham asked me on Gitter to give some feedback. | |
| I think this is a very good idea - so here it is: | |
| 1. When I was first thinking to build a conda package | |
| I had a look into conda-forge and asked myself: "Hey, | |
| what's the difference of uploading packaged to anaconda.org | |
| or publishing them to conda-forge?" | |
| Maybe you could publish a chapter where you talk about | |
| the differences and advantages. | |
| 2. The "Packaging the License Manually" chaper is not 100% clear to me. | |
| For me it was not 100% clear is the LICENSE.txt file must be included | |
| in the same directory as the meta.yaml or not. Even when it is included | |
| in the tarball. | |
| See here: https://conda-forge.org/docs/meta.html#packaging-the-license-manually | |
| 3. Everything else was much to read but good and understandable to me. | |
| Thanks for your work | |
| Philip |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment