Josh Triplett:
> [..]
>
> While I *would* like to see support for version intervals, this
> particular issue is a bug introduced through changes to debcargo. The
> original debcargo intentionally generated versioned dependencies on
> packages like librust-slab-0.3+default-dev rather than
> librust-slab+default-dev. That would prevent this issue. [..]
> Re-adding that will eliminate this issue.
>
Josh, I'm well aware of what the previous debcargo behaviour was and it doesn't
eliminate this issue, as I tried to explain in my previous comment:
I wrote:
> In the Debian Rust team, we previously experimented with e.g. converting:
>
> - Cargo dependencies X (>= 6, << 7) into dpkg dependencies X-6 | X-7
> - Cargo dependencies X (>= 6) into dpkg dependencies X-6 | X-7 | X-8 |
> X-9 | X-10
>
> but this causes other problems (unwieldy dependency conversion logic) and does
> not really solve the problem described within this bug report, since it is
> perfectly legal for separate Cargo crates to declare (= 6.1) (= 6.2) (= 6.3)
> dependencies and Cargo will require all three to be installed even though they
> are (supposed to be) semantically compatible. In this case, we would have to
> create new Debian packages called X-6.i (Provides: X-6 = 6.i) for i={1,2,3}
> which puts us right back where we started. (Although granted it is unlikely,
> assuming that everyone in the Rust ecosystem is sane and avoids this forever.)
You haven't been following the latest developments which are plentiful; please
take some time to get up-to-date before confusing the discussion with
irrelevant information.
I made the decision to do it the current way and diverge from the previous
approach, where we generate dependencies based on versionless-package-names,
based on a request from Sylvestre Ledru about the long-term maintenance of rust
packages. I've been auto-building hundreds of variations of these Rust packages
for the past few months; I'm well aware of the repercussions of both approaches
and don't need to be reminded. After implementing Sylvestre's request I do
think it's much cleaner; and the old way doesn't solve the problem it just
hides it under the carpet and we will have to deal with it eventually anyway.
Let's please get back on topic.
X
--
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git
