Currently cargo-deb only packages assets in the release profile. e.g. /target/release/...
My PR enables to create packages from debug or custom profiles. e.g. /target/my_custom_profile
ive added a --profile application argument option. to keep terminology consistent with cargo
if no --profile argument is given, default to release
You could work around this by creating an [package.metadata.deb.variants.$name] for each permutation, manually writing out the correct path to the assets. but in projects with x profiles times y projects this is not nice..
kornelski
commented
2 years ago
Hello! please consider the following PR :)
Currently cargo-deb only packages assets in the release profile. e.g. /target/release/...
My PR enables to create packages from debug or custom profiles. e.g. /target/my_custom_profile
--profileapplication argument option. to keep terminology consistent with cargo--profileargument is given, default toreleaseYou could work around this by creating an
[package.metadata.deb.variants.$name]for each permutation, manually writing out the correct path to the assets. but in projects withx profilestimesy projectsthis is not nice..