From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: John Soo <jsoo1@asu.edu>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: rust (build system) deficits
Date: Mon, 9 Mar 2020 15:50:50 +0100 [thread overview]
Message-ID: <25ad6a33-2f37-4ea4-6c74-842bbfa46475@crazy-compilers.com> (raw)
In-Reply-To: <B6D563E9-BDB9-4DE8-8CEB-DFF2DA6AA170@asu.edu>
Am 09.03.20 um 15:00 schrieb John Soo:
>> - 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! […] 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?
My point is less the work, but the non-transitive declarations:
nettle-sys is an multi-indirect input for sequioa-sqv, still the later
needs to specify these dependencies.
This importer does not solve the declarations, and IMHO it should not
anyway - as the are dependencies of another packages, which might change
over time.
> Want to compare notes? What are you working on?
Sure: <https://gitlab.digitalcourage.de/htgoebel/guix/-/tree/HG-squoia>
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2020-03-09 14:51 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
2020-03-09 14:50 ` Hartmut Goebel [this message]
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=25ad6a33-2f37-4ea4-6c74-842bbfa46475@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
/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.