Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capture conda build version #35

Open
CJ-Wright opened this issue Mar 3, 2018 · 0 comments
Open

Capture conda build version #35

CJ-Wright opened this issue Mar 3, 2018 · 0 comments

Comments

@CJ-Wright
Copy link
Member

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant