From: David Craven <david@craven.ch>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 1/2] gnu: Add cargo.
Date: Sat, 31 Dec 2016 01:21:48 +0100 [thread overview]
Message-ID: <CAL1_immOWLC+Nbj=egHKYo3mj=SgM+zef6F5RmuCgjiYioOKkg@mail.gmail.com> (raw)
In-Reply-To: <87wpeh55cp.fsf@gmail.com>
> I understand that this is some sort of mechanism to enable cargo to build things
> offline, but is it appropriate to put all of those other packages'
> source into the "cargo" package that is going to be built by Guix? I
> haven't been following the Cargo/Rust in Guix discussion thread, so it's
> entirely possible I just missed something that was already discussed.
No it is not appropriate. There has been a lot of discussion if it is ok to take
shortcuts or not, I think the general opinion is that it is not ok.
But it is a way to
build cargo without a lot of work, since there are a couple of issues that need
to be addressed by the cargo-build-system, specifically the importer.
> OK. That makes sense. But I wonder why cmake and pkg-config are
> missing from the list of references if that is the case?
Wow, I don't know what I was thinking, I was convinced that cmake and pkg-config
where retained inputs :) They should be propagated-inputs then... Thanks!
next prev parent reply other threads:[~2016-12-31 0:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 15:34 [PATCH 1/2] gnu: Add cargo David Craven
2016-12-29 15:34 ` [PATCH 2/2] build-system: cargo: Use correct cargo David Craven
2017-01-02 21:12 ` Ludovic Courtès
2016-12-30 21:58 ` [PATCH 1/2] gnu: Add cargo Chris Marusich
2016-12-30 23:11 ` David Craven
2016-12-31 0:07 ` Chris Marusich
2016-12-31 0:21 ` David Craven [this message]
2016-12-31 2:31 ` Chris Marusich
2017-01-02 21:07 ` 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='CAL1_immOWLC+Nbj=egHKYo3mj=SgM+zef6F5RmuCgjiYioOKkg@mail.gmail.com' \
--to=david@craven.ch \
--cc=cmmarusich@gmail.com \
--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).