Closed h-vetinari closed 4 years ago
Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found some lint.
Here's what I've got...
For recipe:
meta.yaml
, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint .
from the recipe directory. 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.
I do have some suggestions for making it better though...
For recipe:
@conda-forge-admin, please rerender
The two extant patches have been upstreamed by @minrk in DrTimothyAldenDavis/SuiteSparse#7 & DrTimothyAldenDavis/SuiteSparse#8, so I removed them outright.
@conda-forge/suitesparse This is green and should allow to close all open PRs. Next step: windows builds. ;-)
PS. Link to the discussion about the conda-smithy warning regarding license identifiers.
Thanks @h-vetinari. Not having the patches should make future automatic updates easier!
@grlee77: Thanks @h-vetinari.
Happy to help. I want to fix the suboptimal cvxopt build (currently building and statically linking suitesparse for windows within that recipe), so it made sense to start here. In turn, this also means that cvxopt already knows how to build suitesparse for windows, so I'm hopeful I can leverage that (somehow) into a windows build here (cf. #51).
Not having the patches should make future automatic updates easier!
All credit for that belongs to @minrk! :)
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)This picks up the fixed patches from @minrk in #61, together with the version bump from #63.
Closes #60 Closes #61 Closes #62 Closes #63