[Pkg-rust-maintainers] Packaging software written in Rust

Angus Lees gus at debian.org
Mon Jul 18 01:40:00 UTC 2016


I need to go read the patch/PR again, but I'm still unclear whether any of
https://github.com/rust-lang/cargo/pull/2857 allows for *modified* local
registries (ie: those where the contents are not a strict, hash-identical
subset of crates.io).

The main hurdles (as I see them) are:
- some sort of cargo support for local *possibly patched* registries
- some sort of toolchain for easily generating/maintaining Debian packages
for crates.  Doesn't have to be fancy, just better than making 50 packages
by hand.
- we probably need a conversation/policy around library versions.  It's
easy for a cargo package to need multiple versions of a single crate, and
we need to work out how much we want to accommodate that versus patching
applications/libraries to use a narrower set of versions.
- an application package that provides motivation (git-series!)

Fwiw, in my earlier testing I found it easy to make cargo fail if it tries
to access the network by just setting a bogus http_proxy env var.

I did some work earlier towards a "cargo debmake" subcommand (
https://github.com/anguslees/cargo-debmake) but I got lost in trying to add
something like Alex's directory registries PR to cargo (before that PR came
out) and made little further progress.  It may be easier to just start

Re helping: Yes, any of it would be helpful!  I guess first we hack things
up until git-series will compile from crates provided via a central on-disk
registry - and then we worry about making that pretty.

 - Gus

On Mon, 18 Jul 2016 at 10:45 Josh Triplett <josh at joshtriplett.org> wrote:

> I've just released git-series
> (https://github.com/git-series/git-series), a git tool written in Rust.
> git-series tracks the "history of history", tracking changes to a patch
> series over time through rebases and other non-fast-forwarding changes.
> I wrote git-series to help with the maintenance of distribution
> packages, backports, patch series for submission (PATCHv2, PATCHv3,
> ...), and other development processes that may want to rewrite history.
> In particular, git-series avoids having to pull patches out of git and
> into something like quilt in order to version them.
> I'm interested in packaging git-series (and its dependencies) for
> Debian.
> We previously discussed the process of packaging Rust software for
> Debian.  Since then, Alex Crichton wrote a new version of cargo support
> for "local registries" and "directory registries" (see
> https://github.com/rust-lang/cargo/pull/2857), which I think should
> support the approach of packaging libraries as source.  In addition,
> https://github.com/rust-lang/cargo/pull/2811 adds a flag to cause Cargo
> to fail if it would access the network.
> Other than those Cargo pull requests, what would need to happen to make
> it possible to package software written in Rust for Debian?  And how can
> I help?
> - Josh Triplett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-rust-maintainers/attachments/20160718/9f850596/attachment-0001.html>

More information about the Pkg-rust-maintainers mailing list