all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ivan Petkov <ivanppetkov@gmail.com>
To: guix-devel@gnu.org
Subject: Current state of cargo-build-system
Date: Sun, 20 Jan 2019 16:11:58 -0800	[thread overview]
Message-ID: <0FA91CF1-5040-4175-9347-7FEF74CCD725@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

Hello Guix!

I'm new to both Guix and Guile/Scheme and decided to get my feet wet by
attempting to package a non-trivial Rust crate into Guix.

This seems like something others have tried before me with varying degrees of
success (I found this thread from a few years ago which doesn't seem to have
resolved in any way https://lists.gnu.org/archive/html/guix-devel/2017-01/msg00306.html <https://lists.gnu.org/archive/html/guix-devel/2017-01/msg00306.html>).
I ran into a host of issues myself, but I was able to prototype some changes
which allowed me to make some progress. Happy to keep hacking on this, but
ultimately I need some insight/guidance on the proper ways to build this out in
Guix :)

But before I propose any new changes, I wanted to check, what is the current
state cargo/crates in Guix from a community perspective?

Are there any philosophical or technical blockers that preclude pulling in
packages from crates.io, or is it just a matter of chipping away at the problem?

--Ivan

[-- Attachment #2: Type: text/html, Size: 1711 bytes --]

             reply	other threads:[~2019-01-21  0:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21  0:11 Ivan Petkov [this message]
2019-01-23 10:50 ` Current state of cargo-build-system Ludovic Courtès
2019-01-23 11:46   ` ng0
2019-01-23 17:10 ` Danny Milosavljevic
2019-01-25 23:57   ` Ivan Petkov
2019-01-27 23:13     ` Ivan Petkov
2019-01-28  8:44     ` Ricardo Wurmus
2019-01-28 16:23       ` Ivan Petkov

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=0FA91CF1-5040-4175-9347-7FEF74CCD725@gmail.com \
    --to=ivanppetkov@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 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.