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: Wed, 11 Mar 2020 18:55:54 +0100 [thread overview]
Message-ID: <3b6049fb-6cc3-f936-bf2f-d8b31d558221@crazy-compilers.com> (raw)
In-Reply-To: <F4680571-8618-4EA4-8B69-0987FE547B60@asu.edu>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
Hi John,
>> 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.
>>
> I’m not sure I fully understand why the recursive importer should not
> solve the transitive dependencies. Could you elaborate further?
>
> If you are suggesting that guix refresh won’t pick up the changes,
> then I think agree with you. That I believe is an artifact of using
> arguments rather than inputs to specify dependencies.
>
I was talking about `guix import crates -r`, which - like `guix refresh`
- shall not add transitive dependencies to #crate-inputs.
But I would expect the build-system to transitivly resolve #crate-inputs
as well as #crate-development inputs.
> The importer does solve the transitive dependencies but there is a bug. Version numbers of cargo dependencies are not used which can sometimes cause the problem you describe. I really hope the fixes get merged soon because it is a real pain.
Are you talking about "guix import crates" here, too?
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 2121 bytes --]
prev parent reply other threads:[~2020-03-11 17:56 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
2020-03-09 17:48 ` John Soo
2020-03-11 17:55 ` Hartmut Goebel [this message]
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=3b6049fb-6cc3-f936-bf2f-d8b31d558221@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.