Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support `boa` recipe format
See original GitHub issueYour question:
I would like to start a discussion to see if we can support the new recipe format of boa and use it directly for builds. We’ve been using boa in the RoboStack project quite successfully for a while now and I think it would be nice to (optionally!) support the new recipe format in conda-forge as well.
I am listing a couple of points that we’ll need to fix & improve in the boa & conda-forge projects to turn this into reality:
- boa needs to create correct and compatible hashes. To this point I would actually like to do things slightly different vs. conda-build. conda-build deeply inspects all build scripts to find used variables using regex’s. I don’t think that’s a good idea and we already have very good hash input from the build & host environment +
CONDA_BUILD_SYSROOT+channel_targets+target_platform(the latter three are also hard-coded in conda-build, but scattered in multiple places). - conda-smithy needs support for parsing
recipe.yamlinstead ofmeta.yaml(this should be quite straightforward as it’s always “pure yaml”) - the autotick bot would also need to be aware of the new recipe format
I’d be happy to hear what others think! Obviously, we’ll also have to work more on documentation of the entire boa project.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:25 (25 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah a top-level key with the version seems useful from a parsing standpoint.
Well the way this started out was with an attempt to make a spec with lots of community input: https://hackmd.io/axI1tQdwQB2pTJKt5XdY5w
Unfortunately besides myself not many people have invested more time into this 😃 I would hope that changes once we make some additional inroads in conda-forge (and once you try it I don’t think you want to go back, except for complicated recipes).
We have a spec implementation using
pydanticin the repository: https://github.com/mamba-org/boa/blob/master/boa/schemas/model.py – might need a bit more love but the general stuff is there.I can write a more formal CEP but I’d like to also encourage people to try out what’s already there.