[Pkg-rust-maintainers] Bug#786836: packaging not yet ready for mass/stable usage

[Luca Bruno]

On Wednesday 08 July 2015 01:42:43 Angus Lees wrote:

> Do we have a list of what we're waiting for before allowing rustc to
> migrate to testing?

My very-subjective list is:
 1. a working rustc+cargo combo for casual devs/users
 2. a draft idea/experiment on how to tackle crate packaging
 
> I guess specifically:
> - is rustc.deb useful without cargo.deb?

Personally, I would answer "no" here.

> - Do we have any areas of concern that we will find it difficult to migrate
> away from if/when a better alternative shows up?

ATM, I'm curious to see how well the libstd-rust-<hash> update will work after 
next release, and stabilize that. (BTW, thanks for working on 1.1)

Theoretically, I think the next hurdle could be stuff that sits in-between 
different domains (like crates making use of FFI or purposely exposing 
C-compatible interfaces). But I think this is not a strong point right now.

> (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).

I'm usually cautious, but I mostly agree with this.
I think that during the 1.2 window we could have both a working cargo and some 
experience with the whole libstd/dynlibs story, and let rustc+cargo enter 
testing. Does this sound ok for you? 

Cheers, Luca

-- 
 .''`.  ** Debian GNU/Linux **  | Luca Bruno (kaeso)
: :'  :   The Universal O.S.    | lucab (AT) debian.org
`. `'`                          | GPG: 0xBB1A3A854F3BBEBF
  `-     http://www.debian.org 	| Debian GNU/Linux Developer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-rust-maintainers/attachments/20150720/041e2f26/attachment.sig>