From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] gentoo-crate-dist mirror experiment
Date: Tue, 11 Feb 2025 10:25:14 +0100 [thread overview]
Message-ID: <5db027d7de41a66424c131b179a2163b7a783766.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
reply other threads:[~2025-02-11 9:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5db027d7de41a66424c131b179a2163b7a783766.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox