[Pkg-rust-maintainers] Packaging cargo

[Angus Lees]

(Stray '\' on the end of that URL.  Try:
https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=pkg-rust/cargo.git;a=commitdiff;h=82bc382c3005789da6a32ded36e9909f10707454
)

On Sun, 22 Mar 2015 at 00:02 Angus Lees <gus at debian.org> wrote:

> Uploaded what I've got so far:
>
> https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=pkg-rust/cargo.git;a=commitdiff;h=82bc382c3005789da6a32ded36e9909f10707454\
>
> I'm building against upstream git commit
> 57730649d2593879a37becf8a535246014cac1ef, which appears to build with our
> alpha.2 rustc - although some of the unittests fail (I haven't checked why).
>
> Current packaging builds with 'bootstrap' build profile (which downloads
> prebuilt cargo at build time, just as regular upstream Makefile does), and
> then can build itself again with the bootstrapped cargo as a build-dep (or
> should be able to, my first test just now fails because I don't install
> ca-certificates on !bootstrap - but also see next paragraph).
>
> Currently that second rebuild uses a local cargo+rustc, but still
> downloads dependent rust libraries at build time, which is obviously not
> ok.  My plan here is to invent a way to place source (and possibly
> .rlib/dylib in the future) files into cargo's search path, and to add a
> flag that will make cargo fail rather than attempt to download any
> non-local files.  Then I'll need to package up the dozen-or-so libraries
> that cargo requires using that technique, and add then as build-deps (with
> !bootstrap).  This should be done with the cooperation of upstream - I was
> just waiting until I had reached a basic functional cargo.deb first (which
> I think I've now done).
>
> There are still various lintian errors that need to be addressed,
> including adding a debian/copyright file.
>
>  - Gus
>
> On Sat, 7 Mar 2015 at 09:30 Luca Bruno <lucab at debian.org> wrote:
>
>> Hi,
>> in the non-recent past I tried approaching cargo from a packaging POV,
>> but the
>> times were not mature enough.
>>
>> I think that at alpha2 stage we should really focus on re-evaluating it
>> and
>> reporting/fixing bugs.
>>
>> Angus, I know you have some preliminary package, which I'd like to check.
>> I've created an empty git repository at:
>> http://anonscm.debian.org/cgit/pkg-rust/cargo.git/
>> Can you push your personal WiP branch there? (I normally call them with a
>> wip/
>> or lucab/ prefix to quickly distinguish them)
>>
>> Don't worry about quality, this mostly for a starting base to discuss.
>> I'm particularly interested in:
>>  * what to use as a tarball (original tarball? a frozen one with all libs
>>    inside?)
>>  * cargo bootstrapping process (cargo needs cargo!)
>>  * system integration (sysroot, dynlib/rlib, etc.)
>>  * bug hunting for possible blockers
>> First-hand comments and experiences are welcome.
>>
>> Ciao, Luca
>>
>> --
>>  .''`.  ** Debian GNU/Linux **  | Luca Bruno (kaeso)
>> : :'  :   The Universal O.S.    | lucab (AT) debian.org
>> `. `'`                          | GPG Key ID: 0x4F3BBEBF
>>   `-     http://www.debian.org  | Debian GNU/Linux Developer
>> _______________________________________________
>> Pkg-rust-maintainers mailing list
>> Pkg-rust-maintainers at lists.alioth.debian.org
>> https://lists.alioth.debian.org/mailman/listinfo/pkg-rust-maintainers
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-rust-maintainers/attachments/20150321/875a4030/attachment.html>