unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Maxime Devos <maximedevos@telenet.be>, Guix-devel <guix-devel@gnu.org>
Subject: Re: Antioxidant (new rust build system) update - 100% builds
Date: Sun, 6 Nov 2022 11:14:30 +0200	[thread overview]
Message-ID: <Y2d69llrdaWlIDYA@3900XT> (raw)
In-Reply-To: <877d0dvc0h.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]

On Wed, Nov 02, 2022 at 12:20:14PM +0100, Ludovic Courtès wrote:
> Hi!
> 
> Maxime Devos <maximedevos@telenet.be> skribis:
> 
> > 100% (rounded up) of the packages build with antioxidant, though a
> > very few still fail to build:
> > <https://ci.guix.gnu.org/eval/749079/dashboard>.
> 
> Woohoo!!
> 
> > So far, work on antioxidant has been done in a separate channel for
> > convenience, but given that almost everything builds now, I think it's
> > a good time to start looking into moving it into Guix proper
> > (initially as a branch, as there are some remaining TODOs like
> > e.g. 'why are some of the binaries made with antioxidant larger than
> > with cargo-build-system + fix that').
> >
> > More concretely, this would mean changing the 'runtime'
> > transformations done by 'antioxidant-packages.scm' (in the style of
> > '(guix)Defining Package Variants') to source code transformations
> > ("guix style").
> >
> > IIRC, Ludo' has some "guix style" patches for moving #:cargo-inputs to
> > 'inputs' and such; those could perhaps be used as a basis.
> 
> 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?
> 
> Efraim, thoughts on this?

Would it be possible to create a branch for it on savannah and hack on
the integration there? Then we can make sure everything looks good and
merge it in after everything builds nicely.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2022-11-06 10:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29 19:38 Antioxidant (new rust build system) update - 100% builds Maxime Devos
2022-10-29 20:26 ` Tobias Geerinckx-Rice
2022-10-31  1:13 ` Csepp
2022-11-01 16:28 ` Hartmut Goebel
2022-11-02 11:20 ` Ludovic Courtès
2022-11-02 11:33   ` Maxime Devos
2022-11-03 15:16     ` Ludovic Courtès
2022-11-05 22:50       ` Maxime Devos
2022-11-06  9:14   ` Efraim Flashner [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y2d69llrdaWlIDYA@3900XT \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).