Closed jankatins closed 7 years ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
Ok, version using cl.exe from VS is currently building here...
gcc: 24kb cl.exe: 124kb
:-(
I didn't realize we had a miktex package. Interesting! I'll look at the changes later tonight.
@janschulz : Yes, I'd prefer to move the m2-
(and m2w64-
) packages to conda-forge. But it's a matter of time, a resource I've got very little of at present. However if someone wants to move towards getting them on there then I'll happily assist.
Other than reformatting the recipes, setting a repo up for each and kicking off builds, the other thing that needs doing is to merge the pretty messy python script I wrote to generate conda-recipes from MSYS2 packages into conda skeleton
. I also need to know how to use conda-forge a bit better and figure out how the special nature of the m2*
packages fits into the infrastructure [1].
We keep meaning to talk about MSYS2 at the conda-forge hangout meetings, and I'm not sure if it's in-scope for the toolchain meeting tomorrow.
Until then, you should add msys2
to your .condarc
or specify it on the command line as -c msys2
[1] There's a special msys2-conda-epoch
metapackage to enforce lock-step updating to ensure binary compatibility due to the rolling nature of the upstream MSYS2
distro.
Would this compile faster, because the current version took almost 5 minutes at install time, which almost defeats the purpose of using conda here?
You mean the actual install of the package? -> the compile step happens on appveyor. I have the feeling that this depends in the number of files in the package :-(
And it builds :-)
Wrapper stolen from the r launcher in https://github.com/conda/conda-recipes/blob/master/r-base/launcher.c
Closes: https://github.com/conda-forge/miktex-feedstock/issues/10