OK with me, I’ve largely switched to condo/bioconda already.
Chris
> On 18 Oct 2018, at 13:14, rdkit-discuss-requ...@lists.sourceforge.net wrote:
>
> Message: 1
> Date: Thu, 18 Oct 2018 08:33:56 +0200
> From: Greg Landrum mailto:greg.land...@gmail.com>>
> To: RDKit Discuss
Does being in conda-forge mean the package will eventually make it to the
mainline conda repo?
I just have memories (admittedly from when dinosaurs walked the earth) of
upgrading a package from rpmforge and having it brick my Linux machine. And
I still sometimes see a conda-forge install change a
I am happy with conda forge :-). And thanks for the great work.
Markus
On Thu, Oct 18, 2018 at 5:46 PM Greg Landrum wrote:
> Um, guys, there are some interesting side conversations starting here, but
> can we please keep this thread on the "is it ok for me to stop doing builds
> on the RDKit
On Thu, Oct 18, 2018 at 2:21 PM Eric Jonas wrote:
> Greg, I'm all for anything that makes the release process on developers
> easier; my main question is : With conda-forge, how hard is it to install
> just _one_ package without having everything else (say numpy, pandas, etc)
> upgraded to the
Dear Greg,
We should simplify for sure and have a main stream release, so Making a “basic”
release already increase of the toolkit.
Also, that would be interesting to have a “special” contributors releasing
thing cause we need to be agile on that part too.
BR,
Guillaume
De : Eric Jonas
Greg, I'm all for anything that makes the release process on developers
easier; my main question is : With conda-forge, how hard is it to install
just _one_ package without having everything else (say numpy, pandas, etc)
upgraded to the latest conda-forge version? I've had situations in the past
6 matches
Mail list logo
