Skip to content

Conversation

stappersg
Copy link
Contributor

Now results cargo deb in a .deb being build.
The debian package has the binaries stalwart and stalwart-cli.

For what it is worth:
cargo-deb finds out that "stalwart" is the default rust package. That rust package "stalwart-cli" is needed to be build is also something that cargo-deb figures out.
To be able to do cargo deb you first have to do cargo install cargo-deb

Now results `cargo deb` in a .deb being build.
The debian package has the binaries stalwart and stalwart-cli.

For what it is worth:
cargo-deb finds out that "stalwart" is the default rust package.
That rust package "stalwart-cli" is needed to be build is also
something that cargo-deb figures out.
To be able to do `cargo deb` you first have to do `cargo install cargo-deb`
@stappersg
Copy link
Contributor Author

Having [package.metadata.deb] section makes making a very basic .deb possible. Because it is ignored by other tools as cargo-deb does it not harm existing workflows in development of stalwart.

See https://github.com/helix-editor/helix/blob/master/helix-term/Cargo.toml#L15 for "prior art".

@mdecimus mdecimus closed this Aug 18, 2025
@mdecimus
Copy link
Member

Thanks for the PRs but the project is not accepting contributions at this moment, see https://github.com/stalwartlabs/stalwart/blob/main/CONTRIBUTING.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants