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
In gtk-rs we have various git submodules that are only necessary for running the code generator. That is, they're not necessary for compiling the crates inside the repository.
If a crate currently depends on a git version of gtk-rs then cargo will download all those (not very small) git submodules too, unnecessarily.
That it downloads all git submodules currently as a default seems like reasonable behaviour as they might be required for building the crates, but it's not optimal in all cases.
Proposed Solution
Something like the following in Cargo.toml for the repository example above
For backwards compatibility reasons this would obviously default to fetch = true.
Notes
No response
The text was updated successfully, but these errors were encountered:
sdroege
added
the
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
label
Sep 3, 2022
Thanks for the suggestion! I believe this is essentially a duplicate of #4247, so closing in favor of that. If possible, you can adjust the submodule update strategy in .gitmodules.
Thanks, I was not aware of the configuration in .gitmodules. I believe this would work but I'll have to try that. Apart from that, yes this is a duplicate of that other issue :)
Problem
In gtk-rs we have various git submodules that are only necessary for running the code generator. That is, they're not necessary for compiling the crates inside the repository.
If a crate currently depends on a git version of gtk-rs then cargo will download all those (not very small) git submodules too, unnecessarily.
That it downloads all git submodules currently as a default seems like reasonable behaviour as they might be required for building the crates, but it's not optimal in all cases.
Proposed Solution
Something like the following in
Cargo.toml
for the repository example aboveFor backwards compatibility reasons this would obviously default to
fetch = true
.Notes
No response
The text was updated successfully, but these errors were encountered: