Open
Conversation
Member
|
I'd be willing to be added as a maintainer in conda-forge; I don't have the expertise to do much more than approve things their bot does, but I already do that on another repo and occasionally I make myself useful. |
cf3d1e0 to
9c4fcd3
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
LSDB, the LINCC Frameworks tool for spatial analysis of extremely large astronomical databases, depends on the
lsst-sphgeompackage. In the process of making LSDB conda installable we were required to build a recipe forlsst-sphgeom(and as a consequence forlsst-versions) so they would become conda installable too. The pull request against conda-forge staged-recipes passed all checks and it is out for review. We appreciate any additional feedback!On another note, would any of the
lsst-sphgeomcontributors be willing to be added as a maintainer of the recipe?