unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: ng0 <ng0@libertad.pw>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: rust: Crate Dependencies
Date: Thu, 29 Dec 2016 18:35:05 +0100	[thread overview]
Message-ID: <CAL1_imnr-CO8-bdsV78c+8Q053L3zy8Ni=ocMUt1B5RbofGs6w@mail.gmail.com> (raw)
In-Reply-To: <87k2ai6hko.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me>

> Same here for libc crate after the update, but I guess that's
> because cargo is currently packaged and used from the bootstrap
> rust, which is dated one version before the actual rustc you can
> use now, so 0.13.0 cargo and 0.14.0 rustc.

I submitted some experimental patches to the ML which fix this.

Since you have I assume a web application that is written in rust, and
you want to deploy it using guixsd, I think that vendoring the
dependencies like the example cargo package is what you should do. The
goal of using guixsd is fixing the deployment problem. If you vendor
your dependencies and deploy your application like the example cargo
package you should get an environment that is controlled 100% by your
company. Would be awesome to see some real commercial webapps deployed
using guixsd!

  reply	other threads:[~2016-12-29 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-28 14:51 rust: Crate Dependencies Danny Milosavljevic
2016-12-29 10:49 ` David Craven
2016-12-29 11:12   ` Danny Milosavljevic
2016-12-29 11:35     ` David Craven
2016-12-29 12:33     ` ng0
2016-12-29 17:35       ` David Craven [this message]
2016-12-29 20:10         ` ng0

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_imnr-CO8-bdsV78c+8Q053L3zy8Ni=ocMUt1B5RbofGs6w@mail.gmail.com' \
    --to=david@craven.ch \
    --cc=guix-devel@gnu.org \
    --cc=ng0@libertad.pw \
    /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).