all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: rust work in progress conflicts
Date: Fri, 29 Jul 2016 11:46:31 +0200	[thread overview]
Message-ID: <CAL1_imkUSWVJeHf1nresx_C+Njifo0iuWV2qqV9hEBsxEy0w8g@mail.gmail.com> (raw)

Hi Eric!

Nice!

1. Try using 'guix environment --ad-hoc gcc gcc:lib'.

2. I thought about this. Maybe we could add a cargo subcommand that
interacts with the guix/nix daemon directly [0] and then have a small
cargo-build-system that wraps it. I think this would be neat because
we could avoid repackaging all rust crates and nixos could maybe reuse
it too. Otherwise we are rewriting a lot of stuff that cargo already
does really well (not like python and ruby package managers for
example)


[0] https://github.com/rust-lang/cargo/wiki/Third-party-cargo-subcommands

             reply	other threads:[~2016-07-29  9:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  9:46 David Craven [this message]
  -- strict thread matches above, loose matches on Subject: below --
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 13:35     ` rust work in progress conflicts Ludovic Courtès
2016-05-05 14:46       ` Alex Griffin
2016-05-06  9:05         ` Andy Wingo
2016-05-06  9:15           ` Andy Wingo
2016-05-06  9:59         ` Ludovic Courtès
2016-05-05 15:06     ` ng0
2016-07-28  8:28       ` ng0
2016-07-28 18:31         ` Eric Le Bihan
2016-07-29  9:03           ` Andreas Enge
2016-07-29 11:40             ` Vincent Legoll
2016-07-29 14:37               ` ng0
2016-07-30 10:04             ` Eric Le Bihan

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=CAL1_imkUSWVJeHf1nresx_C+Njifo0iuWV2qqV9hEBsxEy0w8g@mail.gmail.com \
    --to=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 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.