[Pkg-rust-maintainers] Bug#786836: packaging not yet ready for mass/stable usage
gus at debian.org
Wed Jul 8 01:42:43 UTC 2015
Do we have a list of what we're waiting for before allowing rustc to
migrate to testing?
(I worry that we might never reach some poorly defined "perfection" and so
we hold back rustc.deb longer than necessary)
I guess specifically:
- is rustc.deb useful without cargo.deb?
- Do we have any areas of concern that we will find it difficult to migrate
away from if/when a better alternative shows up?
(I don't think we have anything that will be difficult to migrate away
from, and thus we should allow rustc to enter testing as is (and even a
stable release if there was one looming). The package is no different to
any other - and will always be a snapshot-in-time of both Rust and our
ongoing packaging improvements)
On Tue, 26 May 2015 at 08:27 Luca Bruno <lucab at debian.org> wrote:
> Source: rustc
> Version: 1.0.0+dfsg1-1
> Severity: serious
> Even though Rust recently reached the 1.0 milestone,
> compiler and ecosystem packaging still has to reach a
> "ready for the masses" status.
> As some bits are still missing (cargo, external libs) and
> other still under discussion (dynlibs, lang-extensions),
> this bug is left open in order to avoid a premature migration
> to testing.
> -- System Information:
> Debian Release: 8.0
> APT prefers stable
> APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> Pkg-rust-maintainers mailing list
> Pkg-rust-maintainers at lists.alioth.debian.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pkg-rust-maintainers