<div dir="ltr"><div>Uploaded what I've got so far:</div><a href="https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=pkg-rust/cargo.git;a=commitdiff;h=82bc382c3005789da6a32ded36e9909f10707454\">https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=pkg-rust/cargo.git;a=commitdiff;h=82bc382c3005789da6a32ded36e9909f10707454\</a><div><br></div><div>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).</div><div><br></div><div>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).</div><div><br></div><div>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).<br><div><br></div><div>There are still various lintian errors that need to be addressed, including adding a debian/copyright file.</div></div><div><br></div><div> - Gus</div></div><br><div class="gmail_quote">On Sat, 7 Mar 2015 at 09:30 Luca Bruno <<a href="mailto:lucab@debian.org">lucab@debian.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
in the non-recent past I tried approaching cargo from a packaging POV, but the<br>
times were not mature enough.<br>
<br>
I think that at alpha2 stage we should really focus on re-evaluating it and<br>
reporting/fixing bugs.<br>
<br>
Angus, I know you have some preliminary package, which I'd like to check.<br>
I've created an empty git repository at:<br>
<a href="http://anonscm.debian.org/cgit/pkg-rust/cargo.git/" target="_blank">http://anonscm.debian.org/<u></u>cgit/pkg-rust/cargo.git/</a><br>
Can you push your personal WiP branch there? (I normally call them with a wip/<br>
or lucab/ prefix to quickly distinguish them)<br>
<br>
Don't worry about quality, this mostly for a starting base to discuss.<br>
I'm particularly interested in:<br>
* what to use as a tarball (original tarball? a frozen one with all libs<br>
inside?)<br>
* cargo bootstrapping process (cargo needs cargo!)<br>
* system integration (sysroot, dynlib/rlib, etc.)<br>
* bug hunting for possible blockers<br>
First-hand comments and experiences are welcome.<br>
<br>
Ciao, Luca<br>
<br>
--<br>
.''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso)<br>
: :' : The Universal O.S. | lucab (AT) <a href="http://debian.org" target="_blank">debian.org</a><br>
`. `'` | GPG Key ID: 0x4F3BBEBF<br>
`- <a href="http://www.debian.org" target="_blank">http://www.debian.org</a> | Debian GNU/Linux Developer<br>
______________________________<u></u>_________________<br>
Pkg-rust-maintainers mailing list<br>
<a href="mailto:Pkg-rust-maintainers@lists.alioth.debian.org" target="_blank">Pkg-rust-maintainers@lists.<u></u>alioth.debian.org</a><br>
<a href="https://lists.alioth.debian.org/mailman/listinfo/pkg-rust-maintainers" target="_blank">https://lists.alioth.debian.<u></u>org/mailman/listinfo/pkg-rust-<u></u>maintainers</a><br>
</blockquote></div>