all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Soo <jsoo1@asu.edu>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: rust (build system) deficits
Date: Mon, 9 Mar 2020 07:00:56 -0700	[thread overview]
Message-ID: <B6D563E9-BDB9-4DE8-8CEB-DFF2DA6AA170@asu.edu> (raw)
In-Reply-To: <192815e6-7d83-2ef2-1f68-4ae3e0cce04e@crazy-compilers.com>

Hi Hartmut,

> On Mar 9, 2020, at 2:26 AM, Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
> 

A second dependancy is "sequoia-openpgp", which requires rhe lalrpop
parser generator for building.

Now when building `sequioa-sqv`, I need to add all these dependencies again:

- nettle-src, since it is "optional" for nettle-sys - and the phase was
not executed.
- bindgen, since it is required to build nettle-sys
- lalrpop, since it is required for building sequoia-openpgp

That is a lot of work! I know because I did all of those for pijul in this channel github.com/jsoo1/guix-channel.  Want to compare notes? What are you working on? 

Also I found the recursive crate importer very helpful, even if it was imperfect. Are you using the importer or doing the work by hand?

And as Efraim mentioned, optional dependencies in the cargo sense are not optional for guix definitions.

Good luck,

John

  parent reply	other threads:[~2020-03-09 14:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-07 13:46 rust (build system) deficits Hartmut Goebel
2020-03-07 18:41 ` John Soo
2020-03-08 17:16   ` Hartmut Goebel
2020-03-08 20:10     ` John Soo
2020-03-08 20:20       ` John Soo
2020-03-09  9:26       ` Hartmut Goebel
2020-03-09 11:17         ` Efraim Flashner
2020-03-09 14:00         ` John Soo [this message]
2020-03-09 14:50           ` Hartmut Goebel
2020-03-09 17:48             ` John Soo
2020-03-11 17:55               ` Hartmut Goebel

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=B6D563E9-BDB9-4DE8-8CEB-DFF2DA6AA170@asu.edu \
    --to=jsoo1@asu.edu \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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.