Hi,

I'm experimenting with an automated setup to build and distribute crate tarballs for Rust packages in Gentoo. The setup roughly works like
this:

1. We create a fork (or a mirror) of the upstream project repository
in the dedicated GitHub organization [1].

2. crate-dist-mirror action [2] is running in a "cronjob" to fetch new
tags from the upstream repository and mirror them to our repository with
a custom workflow.

3. crate-dist action [3] runs on every pushed tag, creating the crate
tarball and uploading it to the GitHub "release".

This has two benefits:

a. you don't have to build the tarballs yourself -- they are usually
already ready when you get to bumping the package,

b. you don't have to host them yourself.

pycargoebuild has a new `--no-write-crate-tarball` option that (combined
with `--crate-tarball`) takes care of updating the ebuild without
actually creating a crate tarball.

Feel free to ping us if you'd like to have any upstream repositories
mirrored there.


[1] https://github.com/gentoo-crate-dist/
[2] https://github.com/projg2/crate-dist-mirror-action/
[3] https://github.com/projg2/crate-dist-action/

--
Best regards,
Michał Górny


-----BEGIN PGP SIGNATURE-----

iQFGBAABCgAwFiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAmerF3oSHG1nb3JueUBn ZW50b28ub3JnAAoJEGOa2uIyniQO+xMIAL0c6K5KT/pmsECLvMIleQIsO/vMx1sP MRGD7RuiuiVBFhz5RVHvaG76TBLl7APx9W/cPeopPSaJL++y/gMO/CsJ1j+erc3H 5uiqTEt/HxWDG+Jtse7Ao1eSF+C76NdJQd9B1DVEU2WZZ3qnknSNkuE+Wlos4j8M 9GQwqoISi8sX6qEKHO9DOdPMYO1KbzG6m+N17qp+9ePxyjhjs186I+Rs5pUTiElH nvWE2vA07QYv4lXESPsPLh7xNPonY1UnNQXYx4V4olAC25fH4+4GhzhxvKBzl/av D3taJUQwZDbycekVv49Z0fCSjG+8PWOD+h3UMmP5yd8v8zlzMf2iu00=
=td5H
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)