From: Maxime Devos <maximedevos@telenet.be>
To: mail@brendan.scot, guix-devel@gnu.org
Subject: Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system
Date: Mon, 04 Apr 2022 11:26:45 +0200 [thread overview]
Message-ID: <64447e47f2f6233f4542783d3943a61ffbfc4618.camel@telenet.be> (raw)
In-Reply-To: <6312dfb8-b33f-125f-85e8-2fbe19ee1b87@brendan.scot>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
Brendan Tildesley schreef op ma 04-04-2022 om 15:10 [+1000]:
> I would have called it cargone.
>
> Do you believe sidestepping cargo all together like this is a good
> long term strategy? In particular that importing packages will still
> be easy.
The package definitions look almost the same, except for:
* #:cargo-inputs and #:cargo-development-inputs are moved to
'inputs'/'propagated-inputs' and 'native-inputs'
* For a few packages, #:features ~'(...) needs to be added
* antioxidant-build-system doesn't look at version numbers,
so the numbers of variants of packages that needs to be defined
could perhaps be reduced
* Cycles are not supported
The fourth point might make things difficult though I have some ideas
on how to resolve it (without simply disabling tests) (TBI!).
Otherwise, I don't see much complications with importing packages.
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-04 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 5:10 Building hexyl (a rust app) without cargo, with antioxidant-build-system Brendan Tildesley
2022-04-04 9:26 ` Maxime Devos [this message]
2022-04-05 22:28 ` raingloom
2022-04-06 10:10 ` Maxime Devos
-- strict thread matches above, loose matches on Subject: below --
2022-03-31 11:55 Removing #:skip-build? from the crate importer? Maxime Devos
2022-03-31 19:47 ` Hartmut Goebel
2022-03-31 20:06 ` Compiling rust things without cargo (super WIP POC) Maxime Devos
2022-04-02 15:18 ` Building hexyl (a rust app) without cargo, with antioxidant-build-system Maxime Devos
2022-04-05 16:10 ` Maxime Devos
2022-04-06 15:49 ` Hartmut Goebel
2022-04-06 16:06 ` Maxime Devos
2022-05-30 8:23 ` Efraim Flashner
2022-05-30 13:37 ` raingloom
2022-05-30 15:15 ` 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=64447e47f2f6233f4542783d3943a61ffbfc4618.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=mail@brendan.scot \
/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).