From: Maxime Devos <maximedevos@telenet.be>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Removing #:skip-build? from the crate importer?
Date: Sat, 02 Apr 2022 12:53:36 +0200 [thread overview]
Message-ID: <b0e04993ac68735a530025081100398d898ceb9b.camel@telenet.be> (raw)
In-Reply-To: <964a284a-2f3d-689c-78f2-d1f4c9b34f78@crazy-compilers.com>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
Hartmut Goebel schreef op za 02-04-2022 om 11:45 [+0200]:
> [checksum things]
> (Maybe the road to go would be to make cargo less strict here. But
> this requires understanding rust code and cargo.)
FWIW, in
<https://notabug.org/maximed/cargoless-rust-experiments/src/master/antioxidant.scm#L31>
and
<https://notabug.org/maximed/cargoless-rust-experiments/src/master/antioxidant.scm#L97>,
the Cargo.toml is parsed.
By using 'toml.dump' from python-toml, it should be feasible to
automatically strip out all mentions of optional dependencies. That's
another form of ‘less strict’ though.
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-04-02 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 19:07 Removing #:skip-build? from the crate importer? Liliana Marie Prikler
2022-03-31 19:14 ` Maxime Devos
2022-04-02 9:45 ` Hartmut Goebel
2022-04-02 10:53 ` Maxime Devos [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-31 11:55 Maxime Devos
2022-03-31 19:47 ` Hartmut Goebel
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=b0e04993ac68735a530025081100398d898ceb9b.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
--cc=liliana.prikler@gmail.com \
/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).