You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
conda-build version used is easy. It's encoded in a package's about.json, so you don't need to record it at build time.
Binary compatibility is a lot harder. It's different on every platform, and I think you'd need to start up some kind of database to match up symbols provided with symbols used. Conda-build 3's run_exports is a decent approximation, but not truly tracking binary compatibility directly.
The text was updated successfully, but these errors were encountered:
@CJ-Wright commented on Mon Feb 19 2018
I'm not certain if/how possible this is, but it might be nice to capture the conda build version being used and the binary compatibility information.
@msarahan commented on Mon Feb 19 2018
conda-build version used is easy. It's encoded in a package's about.json, so you don't need to record it at build time.
Binary compatibility is a lot harder. It's different on every platform, and I think you'd need to start up some kind of database to match up symbols provided with symbols used. Conda-build 3's run_exports is a decent approximation, but not truly tracking binary compatibility directly.
The text was updated successfully, but these errors were encountered: