[
https://issues.apache.org/jira/browse/CLIMATE-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474755#comment-15474755
]
Alex Goodman commented on CLIMATE-868:
--------------------------------------
Hi [~lewismc],
I am fine with this, however keep in mind that dependencies in conda recipes
are best installed from other conda packages. This means that if we split up
maintenance of podaacpy through a separate podaac anaconda channel, users will
now have to add more channels to search for dependencies in their conda install
workflow.
We also raised the idea of maintaining ocw on conda-forge instead of my own
anaconda channel (CLIMATE-866), and after contemplating this and our new need
to maintain compatibility for python3, I believe this is the way to go.
podaacpy is no exception, and we can easily make it possible for podaacpy
developers to maintain the recipe independently from ocw by specifying the
github usernames of the maintainers in the recipe file.
> Move podaacpy conda recipie to official podaacpy repository
> -----------------------------------------------------------
>
> Key: CLIMATE-868
> URL: https://issues.apache.org/jira/browse/CLIMATE-868
> Project: Apache Open Climate Workbench
> Issue Type: Task
> Components: build process
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Trivial
> Fix For: 1.2.0
>
>
> I am proposing that the podaacpy conda recipe which [~agoodman] put together
> (kudos) should be moved out of the OCW repository and into the official
> podaacpy repository at https://github.com/lewismc/podaacpy
> This is simple, it can be easily updated and built into the CI workflow and
> published over on Podaacpy which is less maintenance for the OCW people.
> [~agoodman] wdyt?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
