From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: antioxidant-build-system can be tested as a channel, + GTK app 'castor' builds
Date: Thu, 02 Jun 2022 18:41:15 +0200 [thread overview]
Message-ID: <a515348be6ba745288400b51533eca1c94e3b979.camel@telenet.be> (raw)
In-Reply-To: <39ec083e8e2532dc8c0734774ee7e80cfa22d4a5.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Maxime Devos schreef op di 31-05-2022 om 11:27 [+0200]:
(b) To get a good grasp on what builds/what not, it would be useful
to build the channel at ci.guix.gnu.org or such. More
concretely,
the CI would grab all cargo-build-system rust apps from (gnu
packages ...),
feed them to the package transformation procedure
'vitaminate/auto',
and build the results. Then we can have a look at a dashboard
like
<https://ci.guix.gnu.org/eval/361030/dashboard>.
I've added a file antioxidant-ci.scm to the antioxidant repo which
automatically produces a list of antioxidated packages (except for
those for that the vitaminate/auto procedure currently cannot grok).
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-02 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 14:22 antioxidant-build-system can be tested as a channel, + GTK app 'castor' builds Maxime Devos
2022-05-30 15:26 ` Ludovic Courtès
2022-05-30 15:31 ` Maxime Devos
2022-05-31 9:27 ` Maxime Devos
2022-05-31 11:06 ` Maxime Devos
2022-06-02 16:41 ` Maxime Devos [this message]
2022-06-02 20:20 ` Maxime Devos
-- strict thread matches above, loose matches on Subject: below --
2022-05-31 17:45 antioxidant-build-system can be tested as a channel, + > " kiasoc5
2022-05-31 18:16 ` Maxime Devos
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=a515348be6ba745288400b51533eca1c94e3b979.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
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).