all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Andy Tai <atai@atai.org>
Cc: 61728-done@debbugs.gnu.org, iyzsong@envs.net
Subject: bug#61728: [PATCH] gnu: flatbuffers: Update to 23.1.21
Date: Sun, 05 Mar 2023 22:45:51 +0100	[thread overview]
Message-ID: <87wn3uoos0.fsf_-_@gnu.org> (raw)
In-Reply-To: <20230302080955.17749-1-atai@atai.org> (Andy Tai's message of "Thu, 2 Mar 2023 00:09:55 -0800")

Hi Andy,

Andy Tai <atai@atai.org> skribis:

> * gnu/packages/serialization.scm (flatbuffers-next): New variable
> as flatbuffers@2.0.0 is depended on by tensorflow-lite so we cannot
> just upgrade directly, so adding current release flatbuffers@23.1.21
> as "next" for flatbuffers
> ---
>  gnu/packages/serialization.scm | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
>
> diff --git a/gnu/packages/serialization.scm b/gnu/packages/serialization.scm
> index 8ab1efd311..5b8f02b184 100644
> --- a/gnu/packages/serialization.scm
> +++ b/gnu/packages/serialization.scm
> @@ -699,6 +699,22 @@ (define-public flatbuffers
>  game development and other performance-critical applications.")
>      (license license:asl2.0)))
>  
> +(define-public flatbuffers-next
> +  (package
> +    (inherit flatbuffers)
> +    (name "flatbuffers-next")

Applied, but I kept the package name “flatbuffers” (the variable name is
fine).

Thanks,
Ludo’.




      reply	other threads:[~2023-03-05 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23  9:15 [bug#61728] [PATCH] gnu: flatbuffers: Update to 23.1.21 Andy Tai
2023-03-02  3:24 ` 宋文武 via Guix-patches via
2023-03-02  6:39   ` Andy Tai
2023-03-02  8:09 ` [bug#61728] [PATCH v2] gnu: Add flatbuffers-next Andy Tai
2023-03-05 21:45   ` Ludovic Courtès [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=87wn3uoos0.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=61728-done@debbugs.gnu.org \
    --cc=atai@atai.org \
    --cc=iyzsong@envs.net \
    /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.