Hello Alex, Sounds awesome! 😀 I will pitch in and test it too!
Thanks for the great effort!! On 22 July 2016 at 19:32, Lewis John Mcgibbney <lewis.mcgibb...@gmail.com> wrote: > Hi Alex, > > Again, dynamite. Thanks for this. Please see my comments below. > > On Fri, Jul 22, 2016 at 6:21 AM, <dev-digest-h...@climate.apache.org> > wrote: > > > > > From: "Goodman, Alexander (398K)" <alexander.good...@jpl.nasa.gov> > > To: "dev@climate.apache.org" <dev@climate.apache.org> > > Cc: > > Date: Wed, 20 Jul 2016 12:25:43 -0700 > > Subject: [ANNOUNCE] new ocw conda package! > > Hi all, > > > > I am pleased to inform you all that we now have a prototype conda package > > for OCW. If you have conda installed (if you don't, then you should!), > > users may now install ocw to their ocw environment using > > > > [snip] > > > > If this proves to be effective then I think we should begin directing > users > > towards this installation method instead of Easy-OCW, since it is far > more > > platform agnostic and directly talks to conda, which is the main > > installation method that's used for most of our dependencies already. > > > Agreed! > > > > Kyo > > has already tested the examples using this installation method on a clean > > OSX system, so we can comfortably say that this at least works for OCW > > standalone / RCMES. > > > > Cool, the testing sounds good so far. I'll also test it out and I will > encourage all GSoC students to do the same. > Thanks > > > > > > Very soon I will be committing the conda build recipes to the main repo, > as > > well as adding some more detailed instructions on how to maintain our > conda > > packages. > > > I see you've implemented the documentation thanks. > > > > For collaboration purposes, we have two options we should decide > > on: > > > > 1) Use my existing anaconda channel (agoodman). To update any packages, > we > > may share a token amongst ourselves and then upload any changes directly. > > > > For the next release there is no reason that we cannot keep it hosted in > your account for the time being. For the next release we can possibly move > it to an Apache channel if they have one. We will need to consult INFRA. > > > > > > 2) Create a new anaconda account / password combination that is shared > > between all of us. The existing packages would need to be copied over. > > > > Please see above. We can consult INFRA and see how far the foundation has > got with this. > > > > > > In the meantime, feel free to test the package install out and let me > know > > which option of the two above you prefer. > > > > > Thanks. > Lewis >
