unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jaeme Sifat <jaeme@runbox.com>
Cc: 67974@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#67974] [PATCH 0/3 rust-team] gnu: Add rust-databake-0.1
Date: Tue, 09 Jan 2024 23:28:17 -0500	[thread overview]
Message-ID: <87a5pdu80u.fsf_-_@gmail.com> (raw)
In-Reply-To: <f0335ca876d4f61c2207354e6a3e234cc5777e5e.1704347462.git.jaeme@runbox.com> (Jaeme Sifat's message of "Thu, 4 Jan 2024 00:51:02 -0500")

Hi Jaeme, Efraim,

Jaeme Sifat <jaeme@runbox.com> writes:

> * gnu/packages/crates-io.scm (rust-databake-0.1): New variable.
>
> Change-Id: I8cd9208d9ac904c66de451d4a6f480d7eb1f4d73
> ---
>  gnu/packages/crates-io.scm | 29 +++++++++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
>
> diff --git a/gnu/packages/crates-io.scm b/gnu/packages/crates-io.scm
> index 74321780ef..aba8711bc7 100644
> --- a/gnu/packages/crates-io.scm
> +++ b/gnu/packages/crates-io.scm
> @@ -18567,6 +18567,35 @@ (define-public rust-dashmap-3
>               (setenv "RUSTC_BOOTSTRAP" "1")
>               #t)))))))
>
> +(define-public rust-databake-0.1
> +  (package
> +    (name "rust-databake")
> +    (version "0.1.7")
> +    (source
> +     (origin
> +       (method url-fetch)
> +       (uri (crate-uri "databake" version))
> +       (file-name (string-append name "-" version ".tar.gz"))
> +       (sha256
> +        (base32 "0flmvn7ym0sz6mkh5mg08vcbxa6kjiknhj9bpspww54lwrr5s5w2"))))
> +    (build-system cargo-build-system)
> +    (arguments
> +     `(#:cargo-test-flags
> +       '("--release" "--"
> +         "--skip=src/lib.rs - (line 27)"
> +         "--skip=src/lib.rs - (line 46)") ; Faulty module import of `bake.'

Thanks for adding a comment, but it's still unclear why this is so.  The
bake module is provided by this very library, right?  I'm not
knowledgeable about Rust, but there's surely a variable we could set to
have it discover by rust?

Efraim, would you know?

-- 
Thanks,
Maxim




      reply	other threads:[~2024-01-10  4:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 21:49 [bug#67974] [PATCH 0/3 rust-team] gnu: Add rust-databake-0.1 Jaeme Sifat via Guix-patches via
2023-12-22 22:11 ` [bug#67974] [PATCH 1/3] gnu: Add rust-synstructure-0.13 Jaeme Sifat via Guix-patches via
2023-12-22 22:11 ` [bug#67974] [PATCH 2/3] gnu: Add rust-databake-derive-0.1 Jaeme Sifat via Guix-patches via
2024-01-04  3:51   ` [bug#67974] [PATCH 0/3 rust-team] gnu: Add rust-databake-0.1 Maxim Cournoyer
2023-12-22 22:11 ` [bug#67974] [PATCH 3/3] " Jaeme Sifat via Guix-patches via
2024-01-04  3:55   ` [bug#67974] [PATCH 0/3 rust-team] " Maxim Cournoyer
2024-01-04  5:45 ` [bug#67974] [PATCH v2REVISION 3/3] " Jaeme Sifat via Guix-patches via
2024-01-04  5:51 ` [bug#67974] [PATCH v3REVISION " Jaeme Sifat via Guix-patches via
2024-01-10  4:28   ` Maxim Cournoyer [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

  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=87a5pdu80u.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=67974@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=jaeme@runbox.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 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).