Skip to content

Cargo: decouple crate from main Cargo.toml workspace #7524

@phip1611

Description

@phip1611

Cloud Hypervisor uses the main Cargo.toml both as crate and as workspace. This has some downsides:

I think I started this discussion two years ago (#5761) but back then @rbradford replied with

Big 👎 for reorganising the source tree - it makes backporting and bug fixes and code archaeology much harder.

in my perception, in retrospective, we would not have an issue with that. Please correct me if I'm wrong! Especially as the code in <repo>/src is very small and most functionality is already in <repo>/vmm. So in my opinion, it would improve the developer experience to decouple things without making any noticeable downsides.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions