[Pkg-rust-maintainers] Getting rid of the NEW step for binaries ?

[Ansgar]

On Thu, 2019-10-17 at 18:57 +0200, Sylvestre Ledru wrote:
> Le 17/10/2019 à 18:52, Ansgar a écrit :
> > Sylvestre Ledru writes:
> > > Moreover, the creation (or deletion) of new packages is automatically
> > > managed by debcargo (our tooling).
> > Why do you need to automatically create/remove binary packages?
> 
> Because it is the way it is managed in Rust packages. This is done to 
> express what the package provides. For now, it has been working very well.

That doesn't answer the question why this is the case.

> > From looking at the package with the insane large Provides field, it
> > seems like it creates empty binary packages to avoid some dependencies
> > on other development packages to safe ~50k of downloads?  I would
> > suggest to just accept the 50k extra downloads for packages for people
> > using the rust development packages rather than creating extra binary
> > packages.
> 
> Sure but this isn't directly related to this discussion. I also do agree 
> that we should address this issue.

Hmm?  Adding new binary packages is the reason why packages end up in
binary-NEW.  So this seems directly related to me.

Ansgar