wiiznokes

Ok thank, I finally found the right endpoint but Android has no doc on that, maybe it change with manufacturer.

I think this should be handled primarily with environment variables. Since there can be several types of packages on the same OS, we are forced to depend on the `cargo...

cargo install also use --release as default

> I'm somehow overlooking where it says that. It just suggests it indeed. My point is just that is my sens, it's more "pretty" to write ``` coord = [...

> "You may also use inline tables where appropriate" That seems like a suggestion to me. That why in my sens, this crate should try to define "appropriate" and use...

> Do you have a link indicating that long descriptions are no longer used in deb packages? The multiline portion of `Description` still seems to be listed here: https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-description Yes...

I added long description again, it no longer write `(none)` when empty because it's not necessary. I also added the command to install the crate when using a custom local...

Also, why not use an enum for the different targets (deb, msi, ...) We could imagine a something like this: ```rust enum BundleSettings { name: Option, deb: Deb(BundleDebSettings), msi: Msi(BundleMsiSettings),...

> I think that instead of these new function being constructors, they should be builder-like functions. It makes the api a lot more flexible, at the small cost of turning...

> However, I don't think having separate constructors for each is required here and just adds unnecessary complexity. I better than ```rust Padding { bottom: 5.0, ..Padding::ZERO } ``` (one...