[Pkg-rust-maintainers] On rust library packages

[Angus Lees]

On Tue, 3 Mar 2015 at 09:41 Luca Bruno <lucab at debian.org> wrote:

> Another two notes on this topic:
>
> * Many Cargo.toml specify a == version for dependencies.
>   We could end up maintaining so many source packages in parallel, which
>   sounds painful. Is there an easy way to do so (preferably without going
>   every time through NEW)?
>

Yeah, I don't know what expedited options are available to us here.  We can
automate the recompilation/upload cycle easily enough, but I imagine the
hard bits are similar to what other language collab teams go through with
maintaining all the python-*, libperl-*, etc packages.

* IIRC cargo has some freeze/package subcommand (can't find the exact name
>   now). Which fetches and bundles all dependencies.
>   As we are using static linking anyway, what about having each package
> manage
>   its dependency?
>

Interesting.  This is effectively shipping source for all dependencies
along with every package.  Sounds like it would work well enough, but we
wouldn't have dependencies expressed in the Debian package graph - so we'd
need some new tools to work out what to rebuild following a security fix,
etc.

I guess ideally whatever we come up with should be a similar workflow for
us to cargo freeze: get upstream, auto-pkg all missing dependencies
somehow, upload packages.  The difference is whether that appears to the
ftp-masters as a flood of packages in NEW, or a single new fat package with
a bunch of separate upstream sources (possibly duplicated with other source
packages) embedded within it.

 - Gus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-rust-maintainers/attachments/20150303/b4746753/attachment.html>