Replies: 2 comments 3 replies
-
You don't need different versions of the Rust compiler, and that would break the packaging CI which relies on git repositories for their source tarballs, and for triggering package builds on git commits. Not to mention how incredibly CPU-intense that would be to rebuild the world for every little commit, and how difficult that'd make reviews. |
Beta Was this translation helpful? Give feedback.
-
Cargo doesn't support nested workspaces (yet?) and few of our projects already use a cargo workspace. So supporting this would need major restructuring, that we don't want to engage with at this point. |
Beta Was this translation helpful? Give feedback.
-
Hi! I see now the cosmic-epoch repo is actually a portal with submodules to individual related repos. I wonder if this can be done in a monorepo style with Cargo workspace. I understand this would be a big change, but there're a few reasons:
iced
andlibcosmic
so we now have to build them and their deps again and again, which increase compile time and total compilation storage needed.Maybe a
Cargo.toml
with workspece configs should be enough? The idea is that related projects still have their own repos (issues, PRs, etc) andcosmic-epoch
repo still links them as submodules, but aCargo.toml
with workspece configs should trick Cargo to consider the submodules as workspace members when we compile them in the directory ofcosmic-epoch
.Beta Was this translation helpful? Give feedback.
All reactions