From: ludo@gnu.org (Ludovic Courtès)
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Rust
Date: Sat, 30 Jul 2016 15:39:29 +0200 [thread overview]
Message-ID: <87bn1fckj2.fsf@gnu.org> (raw)
In-Reply-To: <CAL1_im=17UJgdMDGskSL_1O7d+sWwnrVyjTyPwkrB6qrQ2G1+Q@mail.gmail.com> (David Craven's message of "Fri, 29 Jul 2016 21:10:41 +0200")
David Craven <david@craven.ch> skribis:
>> Can we reasonably expect to bootstrap it from source,
>> using a series of previous Rust versions, or using an
>> alternative implementation?
>
> Currently as Jelle said no. But there is [0] that may be a
> viable option in the future.
>
> [0] https://github.com/thepowersgang/mrustc
That would be great.
>> Having crates available as normal Guix packages is the
>> best option for Guix users: uniform interface, the ability
>> to use ‘guix environment’ and all the tools, transactional
>> upgrade and rollback, etc.
>
> I think with a cargo plugin that interacts with the guix daemon,
The Guix daemon is very low-level, is has no idea what a package is, so
it’d be the wrong place for such things IMO.
What we did for other languages should work here: (1) provide an
importer, and (2) provide a build system (we have ‘guix import cpan’ and
‘perl-build-system’, and so on.)
Ludo’.
next prev parent reply other threads:[~2016-07-30 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 19:10 Rust David Craven
2016-07-30 13:39 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-04 14:50 Rust David Craven
2016-09-07 6:04 ` Rust Eric Le Bihan
2016-03-25 17:45 LLVM: "FileCheck" is missing Danny Milosavljevic
2016-03-25 22:06 ` rust work in progress conflicts (was: Re: LLVM: "FileCheck" is missing) Nils Gillmann
2016-05-04 10:34 ` Jelle Licht
2016-05-05 15:06 ` rust work in progress conflicts ng0
2016-07-28 8:28 ` ng0
2016-07-28 18:31 ` Eric Le Bihan
2016-07-29 15:16 ` Rust Ludovic Courtès
2016-07-29 15:34 ` Rust Alex Griffin
2016-07-29 16:08 ` Rust Jelle Licht
2016-07-30 13:34 ` Rust Ludovic Courtès
2016-07-30 17:57 ` Rust Pjotr Prins
2016-07-30 11:01 ` Rust Eric Le Bihan
2016-07-30 13:44 ` Rust Ludovic Courtès
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=87bn1fckj2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=david@craven.ch \
--cc=guix-devel@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).