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

Fix and test min versions build #363

Merged
merged 3 commits into from Feb 17, 2022
Merged

Fix and test min versions build #363

merged 3 commits into from Feb 17, 2022

Conversation

newpavlov
Copy link
Member

No description provided.

@aewag
Copy link
Contributor

aewag commented Feb 16, 2022

Would 'minimal-versions' maybe also a candidate to be within RustCrypto/actions?

@newpavlov
Copy link
Member Author

@aewag
Yes, I plan to do it a bit later.

@tarcieri
Copy link
Member

@aewag I suggested the same thing here, as it were: RustCrypto/block-ciphers#303 (review)

@newpavlov
Copy link
Member Author

I couldn't port the minimal versions job to a composite action (see RustCrypto/actions#3), so I think I will leave it for a separate PR when the action will be ready.

@aewag
It would be great if you could handle it since it looks like you are more proficient with GitHub Actions than me.

@newpavlov newpavlov merged commit e1a8e86 into master Feb 17, 2022
@newpavlov newpavlov deleted the fix_min_vers branch February 17, 2022 08:56

[features]
default = ["std"]
std = ["digest/std"]
asm = ["sha2-asm"]
compress = [] # Expose compress function
asm = ["sha2-asm"] # WARNING: this feature SHOULD NOT be enabled by library crates
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you clarify why was this warning added?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because if a crate somewhere deep in your dependency tree enables it, it could become virtually impossible to disable it. Considering that the assembly crates may fail to build on some targets (e.g. see RustCrypto/asm-hashes#34), it can be quite unpleasant for users downstream.

In future we may migrate to the configuration flags approach which we now use in some cipher crates, e.g. see the relevant aes docs.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link to the issue is exactly what I was looking for, thanks!

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

Successfully merging this pull request may close these issues.

None yet

4 participants