Open Cadair opened 8 years ago
mwcraig
commented
8 years ago I think the first one to try is astropy; my wild guess is that conda-forge is at least 6 months from being fully stable, so in the short run we'll need our own channel.
The current astropy recipe in github.com/conda/conda-recipes is for v0.2.x so that seems like the low-hanging fruit to pick.
astrofrog
commented
8 years ago @mwcraig - I've been going through the process of setting up conda-forge for glueviz and it was straightfoward and smooth, so I think it's actually already pretty stable. I would actually suggest that we start looking into the possibility of using conda-forge and then copying our built packages over to the openastronomy and/or astropy channels. I opened an issue here to find out how we could copy over the packages to another channel: https://github.com/conda-forge/staged-recipes/issues/593
Can we use the anaconda cloud API to easily copy packages from one channel to another?
kbarbary
commented
7 years ago Any more thoughts on this? It would be good to at least have astropy and astropy-helpers on conda-forge to support building affiliated packages there. (I tried conda-forge for the latest version of sncosmo, but ran into this problem.)
mwcraig
commented
7 years ago Adding astropy and astropy-helpers is the low-hanging fruit that ought to be addressed in the short term. There are still some stability issues with conda-forge, both in terms of the build machinery and stability of the conda-forge set of packages if you install everything from conda-forge.
I won't have time to look at adding astropy and helpers until thanksgiving at the earliest.
Cadair
commented
7 years ago When adding astropy to conda-forge it would be cool to add the c libraries as external packages so they could also be picked up by other things.
So given the recent information on continums potenial adoption of conda-forge, what's the plan for getting the packages in this repository into conda-forge?