Remove most default-members
to speed up builds and reduce duplication
#7494
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We included almost every crate in
default-members
. All crates exceptwindows-installer
which could not build without specific inputs as to what installers to include (it built a full universal installer, bundling arch specific installers at build time). This list had a lot of duplication and seems like a bit of a mess to maintain.Since our workspace also contained virtually everything, a simple
cargo build
built everything, which might not be desired from a build time perspective. This PR reduce thedefault-members
to some "sane default" bare minimum. It includesmullvad-daemon
andmullvad-cli
because those are the main binaries, and anyone building this project is most likely after those binaries. It also includesmullvad-version
since we have a ton of invocations tocargo run --bin mullvad-version
, and that does not work if the crate is not a default crate. We could also update all those invocations to add an extra-p mullvad-version
to solve the issue. But I felt like the version computation binary was central enough to be included as a default crate 🤷This change is