From: Maxime Devos <maximedevos@telenet.be>
To: Nicolas Graves <ngraves@ngraves.fr>, 25327@debbugs.gnu.org
Subject: bug#25327: windows-related dependencies in crates
Date: Thu, 24 Mar 2022 20:10:43 +0100 [thread overview]
Message-ID: <373d643a3526861bd97d3de53b5ec9eb6f21e5f8.camel@telenet.be> (raw)
In-Reply-To: <87h77nyymd.fsf@ngraves.fr>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
Nicolas Graves schreef op do 24-03-2022 om 18:18 [+0100]:
> I included Maxime Devos in the
> conversation, would it be possible to fork guix to develop this and try
> to rebuild every rust package after that on a guix build farm ?
In the past, for some build system changes, separate branches have been
created that are automatically built by ci.guix.gnu.org. A non-
committer and a committer could then collaborate together (on
guix-devel@gnu.org / guix-patches@gnu.org), though only the committer
can
actually push the changes. If, at some point, the changes appear to be
‘ready’, the build on ci.guix.gnu.org can be started to build the
substitutes. If there are no regressions and the builds completed, the
branch can be merged.
TBC, I'm not a committer, but I'd be willing to review FWIW (I don't
understand cargo).
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-03-24 19:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 0:46 bug#25327: cargo build-system should be able to filter out target.cfg(windows) dependencies ng0
2020-12-18 19:56 ` zimoun
2020-12-19 13:10 ` Hartmut Goebel
2021-01-11 12:41 ` zimoun
2021-01-11 13:33 ` John Soo
2022-03-24 17:18 ` bug#25327: windows-related dependencies in crates Nicolas Graves via Bug reports for GNU Guix
2022-03-24 19:10 ` Maxime Devos [this message]
2022-10-08 14:15 ` bug#25327: cargo build-system should be able to filter out target.cfg(windows) dependencies zimoun
2022-10-08 16:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=373d643a3526861bd97d3de53b5ec9eb6f21e5f8.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=25327@debbugs.gnu.org \
--cc=ngraves@ngraves.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.