[
https://issues.apache.org/jira/browse/CLIMATE-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474415#comment-15474415
]
Ibrahim Jarif commented on CLIMATE-866:
---------------------------------------
Hi [~lewismc], https://conda-forge.github.io contains a collection of recipes.
Right now we have to run `conda install -c agoodman podaacpy`. If we use
`conda-forge` then we'll have to run `conda install -c conda-forge ocw`.
We have 2 possible ways to integrate conda build into our existing CI workflow.
1. We could use Travis CI to build conda recipe and then deploy the package on
Anaconda on tagged commits (Just like PodaacPy). The `ocw` package will be
available under agoodman channel.
2. We could setup `ocw` package on `conda-forge`. This might be a bit
complicated as `conda-forge` creates a repo for each recipe. Lets call the repo
for ocw as `ocw-feedstock`. We will need someone to maintain the
`ocw-feedstock` repo. Every time the recipe gets updated the person who owns
the `ocw-feedstock` repo needs to send a PR to `conda-forge`. Only then the
conda package will be updated on Anaconda. The updating of recipe from
`apache/climate` repo to `ocw-feedstock` could be automated. But the PR that
has to be sent manually to `conda-forge`.
We might need something like this if we choose to go with the second option
https://gist.github.com/domenic/ec8b0fc8ab45f39403dd
> Create conda packages against Python3
> -------------------------------------
>
> Key: CLIMATE-866
> URL: https://issues.apache.org/jira/browse/CLIMATE-866
> Project: Apache Open Climate Workbench
> Issue Type: Task
> Components: conda
> Affects Versions: 1.1.0
> Reporter: Lewis John McGibbney
> Assignee: Alex Goodman
> Priority: Critical
> Fix For: 1.2.0
>
>
> Hi [~agoodman], I recently tried to use the conda package to install OCW. I
> am using Miniconda3 and therefore Python3. When I run the conda install, I
> get the following
> {code}
> lmcgibbn@LMC-032857 /usr/local/climate(master) $ conda install -c agoodman ocw
> Fetching package metadata .........
> Solving package specifications: ....
> The following specifications were found to be in conflict:
> - ocw
> - python 3.5*
> Use "conda info <package>" to see the dependencies for each package.
> {code}
> This is because the packages are built using Python 2.7 as per
> https://anaconda.org/agoodman/ocw/files.
> Seeing as all of our CI and smoke testing now runs off of Python 3.X, I
> wonder if you are able to push an update to the conda files which compile
> against Python3?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
