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

Documented about Mamba #1354

Conversation

PrernaSingh587
Copy link
Contributor

@PrernaSingh587 PrernaSingh587 commented Apr 11, 2021

This is a draft PR. I have documented about what mamba build is and how it may prove to be useful.

PR Checklist:

  • make all edits to the docs in the src directory, not in docs
  • note any issues closed by this PR with closing keywords
  • put any other relevant information below

@PrernaSingh587
Copy link
Contributor Author

@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)

@leofang
Copy link
Member

leofang commented Apr 11, 2021

cc: @wolfv

@leofang
Copy link
Member

leofang commented Apr 11, 2021

Looks like this complements to #1353?

@ForgottenProgramme
Copy link
Contributor

Looks like this complements to #1353?

@PrernaSingh587 , nice work there. :)

But, look here Prerna: #1290 (comment)
As commented, I was already working on documenting about mamba.

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.
This way we could avoid two persons working on the same issue. Also, communication could lead to collaboration.
Let's work together, next time? :) <3

@PrernaSingh587
Copy link
Contributor Author

PrernaSingh587 commented Apr 11, 2021

Looks like this complements to #1353?

@PrernaSingh587 , nice work there. :)

But, look here Prerna: #1290 (comment)
As commented, I was already working on documenting about mamba.

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.
This way we could avoid two persons working on the same issue. Also, communication could lead to collaboration.
Let's work together, next time? :) <3

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.

@ForgottenProgramme
Copy link
Contributor

@PrernaSingh587
No problem.
Just put it on Github (comments or an issue) next time, so that others can know too. :)

Copy link
Member

@beckermr beckermr left a 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

@viniciusdc
Copy link
Contributor

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 ?

@beckermr
Copy link
Member

if you want to document build_with_mambabuild, then look at the conda-forge.yml configuration section.

@PrernaSingh587
Copy link
Contributor Author

New PR created #1381

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

Successfully merging this pull request may close these issues.

5 participants