Closed minrk closed 5 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.
LGTM 👍
@jakirkham @grlee77 what do you think?
I am not familiar enough with Makefile
syntax to judge if this is correct, so I would defer to those with more expertise. Two quick questions:
1.) In short, this patch only modifies behavior on OS X and causes the dynamic libraries to use e.g. *.4.5.dylib
rather than the more specific *.4.5.4.dylib
to be used as the install_name
?
2.) Do we know that SuiteSparse
has ABI compatibility between patch versions?
In short, this patch only modifies behavior on OS X and causes the dynamic libraries to use e.g. .4.5.dylib rather than the more specific .4.5.4.dylib to be used as the install_name?
According to the variables in the Makefiles, it would be *.4.dylib
(major only), but otherwise yes.
Do we know that SuiteSparse has ABI compatibility between patch versions?
We know that suitesparse is setting the compatibility version in its dylibs, so at least the libraries themselves claim compatibility at the major version level. I can't speak for the project in general, but a cursory test of a conda package compiled against 4.5.3 updated manually to load 4.5.4 does work.
sorry this PR has gone neglected. I think now the build number should be bumped to 202 since the OpenBLAS update bumped it to 201.
@minrk: Is this otherwise good to go? if interested, please add yourself as a maintainer as well
Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.
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.
According to the ABI report for SuiteSparse it appears that at least 4.5 has been stable across patch release. Before that it was static libraries that are fairly old, which makes it hard to say much about its compatibility during that period.
Should we add a file test to ensure that the library name is as expected?
Good idea, I'll add a few calls to otool -L
that verify the install name is right.
Aside: it would be cool if conda-build test environments could verify compatibility by running the test env with multiple versions of the built package.
In general, a useful pattern for verifying C libs that their linking config is set up correctly:
Sorry for taking so long with the tests. The tests are here now, so we can start getting a suitesparse with correct linking on mac.
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:
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.
This is now also a full conda-build 3 update per @isuruf's request.
Rebased again
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:
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 think this is good to go now (and has been for a year or so). Anything else blocking the merge?
:+1:
Conflicts resolved again, build number bumped again.
All builds have succeeded. This should be ready to go again. Not sure why osx shows as still queued, since it's succeeded a while ago.
I've submitted this patch upstream. Not sure yet if it will be accepted.
closes #22