-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
let's try rust again #64
Conversation
…da-forge-pinning 2021.02.09.18.00.00
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 ( |
This also needs a way to package the licenses of the rust dependencies. |
Can you ask upstream about how to package the licenses of the rust dependencies for a binary package of cryptography? |
Will do! Is there an easy way to get a list of them from the build? Checking the logs I could not see anything obvious? |
xref.: pyca/cryptography#5864 |
@isuruf I'm not a Rust expert but upstream told me to check each Cargo.toml for the licenses. I believe the direct dependency are listed in https://github.com/pyca/cryptography/blob/main/src/rust/Cargo.lock However, we would need to dig into the dependencies of the dependencies and things can get out of hand pretty quickly. Should we just "assume" that the downstream licenses are compatible with cryptography's licenses (Apache-2.0 AND BSD-3-Clause AND PSF-2.0) and that is the responsibility of upstream? Otherwise we will need to either package and handle the rust deps, highly unlikely and probably quite difficult, or we will need to build a tool to extract those licenses. |
There is such a tool. See conda-forge/conda-forge.github.io#1052 for more discussion. |
Below is what I got from cargo-rust. Most deps don't have a license file :-(
|
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 ( 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 ( |
…da-forge-pinning 2021.02.25.09.52.02
@isuruf is the extra directory with the licenses file OK? PS: after going through the process of checking all licenses with cargo-license I have to say that this does not scale. The licenses files usually have the same name, we are pre-pending the project name but that changes from the metadata, the GH name, or even multiple packages in the same repo making sorting the licenses our a bit fuzzy. |
@isuruf should we merge this to "cash" the passing archs and open an issue for osx_arm? |
🎉 Thanks @isuruf!!! |
- ls $PYO3_CROSS_LIB_DIR # [build_platform != target_platform] | ||
- find $PYO3_CROSS_LIB_DIR -name "_sysconfigdata*.py" -not -name "${_CONDA_PYTHON_SYSCONFIGDATA_NAME_BACKUP}.py" -type f -exec rm -f {} + # [build_platform != target_platform] | ||
- ls $PYO3_CROSS_LIB_DIR # [build_platform != target_platform] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These 3 lines can be removed now because this is done in cross-python
now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll remove them tomorrow. Thanks!
Updates the deps and removed those that are for py<36.