unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 46399@debbugs.gnu.org
Subject: [bug#46399] [PATCH] build-system/cargo: Propagate crates across builds.
Date: Sun, 11 Apr 2021 17:11:21 +0200	[thread overview]
Message-ID: <20210411151052.ckjjpbrpqgfp43tl@pelzflorian.localdomain> (raw)
In-Reply-To: <20210209105843.13230-1-efraim@flashner.co.il>

Hello Efraim!

Thank you for improving Rust development with Guix.  I have a question
about this change to doc/guix.texi when translating.  Sorry for
noticing so late just before the string freeze.

On Tue, Feb 09, 2021 at 12:58:43PM +0200, Efraim Flashner wrote:
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 7d18703283..0d153a1470 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> […]
> @@ -7437,8 +7437,10 @@ supports builds of packages using Cargo, the build tool of the
>  It adds @code{rustc} and @code{cargo} to the set of inputs.
>  A different Rust package can be specified with the @code{#:rust} parameter.
>  
> -Regular cargo dependencies should be added to the package definition via the
> -@code{#:cargo-inputs} parameter as a list of name and spec pairs, where the
> +Regular cargo dependencies should be added to the package definition similarly
> +to other packages; those needed only at build time to native-inputs, others to
> +inputs.  If you need to add source-only crates then you should add them to via
> +the @code{#:cargo-inputs} parameter as a list of name and spec pairs, where the
>  spec can be a package or a source definition.  Note that the spec must
>  evaluate to a path to a gzipped tarball which includes a @code{Cargo.toml}
>  file at its root, or it will be ignored.  Similarly, cargo dev-dependencies

I have no experience in Rust.  Do I understand correctly that
source-only crates among the inputs should be added both to inputs and
to #:cargo-inputs?  Is the

> +inputs.  If you need to add source-only crates then you should add them to via

a typo which should read “add them too” instead of “add them to”?

I look at the subsequent change
f35ab79e033aa8e4955e9c9100c74ecbb3ce4d0b to rust-wayland-commons

> diff --git a/gnu/packages/crates-graphics.scm b/gnu/packages/crates-graphics.scm
> index d67e9dc02f..7dde00ffdb 100644
> --- a/gnu/packages/crates-graphics.scm
> +++ b/gnu/packages/crates-graphics.scm
> @@ -2415,8 +2415,11 @@ the wayland protocol, client side.")
>      (arguments
> -     `(#:skip-build? #t
> -       #:cargo-inputs
> +     `(#:cargo-inputs
>         (("rust-nix" ,rust-nix-0.18)
>          ("rust-once-cell" ,rust-once-cell-1)
> -        ("rust-smallvec" ,rust-smallvec-1)
> -        ("rust-wayland-sys" ,rust-wayland-sys-0.28))))
> +        ("rust-smallvec" ,rust-smallvec-1))))
> +    (inputs
> +     `(("rust-nix" ,rust-nix-0.18)
> +       ("rust-once-cell" ,rust-once-cell-1)
> +       ("rust-smallvec" ,rust-smallvec-1)
> +       ("rust-wayland-sys" ,rust-wayland-sys-0.28)))
>      (home-page "https://github.com/smithay/wayland-rs")

and do not understand why rust-wayland-sys is only part of inputs but
rust-once-cell is also among the cargo-inputs.  Also the inputs are
empty for older versions of rust-wayland-commons.

Could you clarify what is written in the doc/guix.texi?

Regards,
Florian




  parent reply	other threads:[~2021-04-11 15:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 10:58 [bug#46399] [PATCH] build-system/cargo: Propagate crates across builds Efraim Flashner
     [not found] ` <handler.46399.B.16128684293899.ack@debbugs.gnu.org>
2021-03-14 17:59   ` bug#46399: Acknowledgement ([PATCH] build-system/cargo: Propagate crates across builds.) Efraim Flashner
2021-04-11 15:11 ` pelzflorian (Florian Pelz) [this message]
2021-04-12  6:40   ` [bug#46399] [PATCH] build-system/cargo: Propagate crates across builds Efraim Flashner
2021-04-13 12:31     ` pelzflorian (Florian Pelz)
2021-04-13 17:49       ` Leo Famulari

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=20210411151052.ckjjpbrpqgfp43tl@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=46399@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    /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).