-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
chrono.clock
feature is not enabled on all crates
#3332
Comments
Why do you want For anything rust related, using the regular crate is likely a better fit, or am I missing something? sqlx = { version = "0.7", features = [ "runtime-tokio", "sqlite"] } |
Fedora packaging policy is to package each crate individually. The main project that I'm trying to package is People tend to disagree with this non-vendored approach, but this has benefits for distro packagers particularly in the control of security patches. |
From https://docs.fedoraproject.org/en-US/packaging-guidelines/Rust/
=> I (not a maintainer) would consider that package as an "internal implementation detail" and choose the cargo workspace projects rules for fedora packaging.
I only see the following. Am I missing something? |
Workspace projects are only used when there is no other package that depends on it. That is because the crates cannot be extracted in the current workflow and sometimes projects do not have version sync on the workspace. Unfortunately For atuin see this section. The direct dependency is |
When running the tests for
sqlx-sqlite
in Fedora packaging I get the following error:This issue is not detected when running from workspace because
sqlx-core
includes theclock
featureand
sqlx-sqlitedepends on
sqlx-core. But when building and testing the
sqlx-sqlite` crate standalone with all features enable, this issue pops up.How about either adding the clock feature to the base workspace dependency or adding those features to each crate? Probably there are some other dependencies with similar issues.
The text was updated successfully, but these errors were encountered: