Re: Antioxidant (new rust build system) update - 100% builds

["Ludovic Courtès" <ludo@gnu.org>]

Hi,

Maxime Devos <maximedevos@telenet.be> skribis:

> On 02-11-2022 12:20, Ludovic Courtès wrote:
>> [. ..]
>> That’s <https://issues.guix.gnu.org/53127> but it probably needs work if
>> we want it to work reliably on all the packages.  My understanding is
>> that we’d need a “flag day” where we’d switch all Rust packages to
>> Antioxydant in one commit, is that correct?  Any ideas how to achieve
>> the big migration?
>
> That's the idea I think, yes.  For this big migration, I propose to
> make the "guix style" good enough to do the switch at once (and let
> ci.guix.gnu.org build it etc. before merging).

OK, makes sense.

> On how to achieve this: the basic antioxidation (e.g. move
> #:cargo-inputs to inputs) is currently fully automated (*).  Then
> there is stuff like 'add this-input to that-package', which is
> 'half-automated', in the sense that there are a bunch of declarative
> alists for that, interpreted automatically but declared manually;
> those could be interpreted by "guix style" as well.

Perhaps we could temporarily support the “old style”, using the run-time
transformation currently in your repo?  That would allow third-party
channels to migrate peacefully, and it would also reduce the likely hood
of breakage during transition in Guix (e.g., if an old-style package is
merged while the new branch is being built.)

Anyway, please do ping people here when specific action is needed from
the rest of us!

Thanks,
Ludo’.