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
Disclaimer: Using "rustc" / "cargo" for the first time.
I found a blog with a reference to zola, and decided to build it.
A huge amount of dependencies where downloaded and build in 7min 39sec,
followed by a big deprecation warning:
Finished `release` profile [optimized] target(s) in 7m 39s
warning: the following packages contain code that will be rejected by a future version of Rust: quick-xml v0.17.2
note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`
I learned (with ps -ax during the build), that "$HOME/.cargo/registry/" is used as build dir,
so i looked there:
From inspecting the directory names, zola depends on a lot of projects (398),
and some of them (24) are included multiple times in different versions:
So 24 packages are downloaded and build multiple times.
The winner is "hashbrown", which is present in 3 versions.
The final executable has no symbols and there is no debug file nearby,
so I have no Idea,
if the duplicate packages are filtered out during linking,
or if they are included in the resulting huge 37MB program multiple times.
$ size zola
text data bss dec hex filename
26232962 12023984 21432 38278378 24814ea zola
I found two rustc versions on my system, but i don't know, which was used.
rustc 1.75.0 (82e1608df 2023-12-21) (built from a source tarball)
rustc 1.80.1 (3f5fd8dd4 2024-08-06) (built from a source tarball)
I have only one cargo version installed:
cargo 1.80.1 (376290515 2024-07-16)
Expected Behavior
rust claims: A language empowering everyone to build reliable and efficient software
Including dependencies in multiple versions in a project is not efficient.
Current Behavior
zola was not used yet, it's just about building enhancements
Avoid to depend on multiple versions of a package
Avoid outdated packages
Step to reproduce
Just build and see the deprecation warning and the duplicate packages.
$HOME/.cargo/registry/src/index.crates.io-6f17d22bba15001f
The text was updated successfully, but these errors were encountered:
As for the other duplicate dependencies, not much we can do except bumping the deps regularly. I did do some PRs to various crates to update things but it's too much work tbh, and the maintainers are not necessarily active
Enhancement request
Disclaimer: Using "rustc" / "cargo" for the first time.
I found a blog with a reference to zola, and decided to build it.
A huge amount of dependencies where downloaded and build in 7min 39sec,
followed by a big deprecation warning:
I learned (with
ps -ax
during the build), that "$HOME/.cargo/registry/" is used as build dir,so i looked there:
From inspecting the directory names, zola depends on a lot of projects (398),
and some of them (24) are included multiple times in different versions:
So 24 packages are downloaded and build multiple times.
The winner is "hashbrown", which is present in 3 versions.
The final executable has no symbols and there is no debug file nearby,
so I have no Idea,
if the duplicate packages are filtered out during linking,
or if they are included in the resulting huge 37MB program multiple times.
Environment
Zola version: git 6d4b110
I found two rustc versions on my system, but i don't know, which was used.
rustc 1.75.0 (82e1608df 2023-12-21) (built from a source tarball)
rustc 1.80.1 (3f5fd8dd4 2024-08-06) (built from a source tarball)
I have only one cargo version installed:
cargo 1.80.1 (376290515 2024-07-16)
Expected Behavior
rust claims:
A language empowering everyone to build reliable and efficient software
Including dependencies in multiple versions in a project is not efficient.
Current Behavior
zola was not used yet, it's just about building enhancements
Step to reproduce
Just build and see the deprecation warning and the duplicate packages.
$HOME/.cargo/registry/src/index.crates.io-6f17d22bba15001f
The text was updated successfully, but these errors were encountered: