-
-
Notifications
You must be signed in to change notification settings - Fork 286
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
Documented about Mamba #1354
Documented about Mamba #1354
Conversation
@viniciusdc Could you please check ? I have briefed about mamba here and added the links for the installation to the original mamba docs. I have added the link on how to use mamba-build to maintainers_faq page. (This will be valid when the mamba-build part gets merged) |
cc: @wolfv |
Looks like this complements to #1353? |
@PrernaSingh587 , nice work there. :) But, look here Prerna: #1290 (comment) It would be better if you could inform other community members (through Github comments) before you start working on any issue or a part of it. |
Yup . @viniciusdc and I had a discussion about this yesterday itself. Moreover this is just a draft PR which I am intending to complement with mamba-build procedure. This one stays in knowledge base. |
@PrernaSingh587 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This text is in the wrong spot. The knowledge base is for recipes
Sorry that was my bad, we were discussing about build with mamba configuration to debug and forgot about that. Maybe this place sounds better https://conda-forge.org/docs/maintainer/adding_pkgs.html#miscellaneous ? |
if you want to document build_with_mambabuild, then look at the conda-forge.yml configuration section. |
New PR created #1381 |
This is a draft PR. I have documented about what mamba build is and how it may prove to be useful.
PR Checklist:
src
directory, not indocs