-
Notifications
You must be signed in to change notification settings - Fork 22
Conversation
Can this be done with plain python or plain bash? |
Probably, PRs welcome. |
We have no xonsh users on staff, so we are not really able to maintain this as is. As you speak xonsh, would you be willing to translate it for us? |
I won't be able to translate this right now. I may be able to later in the week. If there is some interest in learning xonsh here are the docs: Xonsh is fairly intuitive, the deps are very light, and the devs are very responsive. |
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.
remove xonsh usage.
I really love xonsh; I hope it takes over the world; I agree with @tacaswell that this is not a good enough reason to add yet-another-thing that some onboarding member of staff would have to learn in order to maintain our already-complex build stack. Sorry for the thanks-for-the-milk-can-we-have-a-cookie nature of this request, but some help translating this would be great when you have the time! |
@mrakitin this is the PR with auto conda-forge updating. |
@CJ-Wright, thanks, but I'm not sure how we can use it with our current building approach. Can you explain? |
This would issue PRs into lightsource2-recipes with updates from the conda-forge recipes which are in lightsource2. Those PRs could be merged and then building would continue as normal. The main benefit of this is that new versions/updates to recipes from the community would be PRed over to lightsource2-recipes automatically. A potential extension of this would be to build a graph and check that all deps are on lightsource2-recipes or defaults, but that could be done later. |
Closes #255
@jrmlhermitte @danielballan
I think this should work, it worked on my local. Once everyone is happy with this they should:
totally_not_a_travis.yaml
file into a valid.travis.yaml