From: "Ludovic Courtès" <ludo@gnu.org>
To: Franz Geffke <franz@pantherx.org>
Cc: 63296@debbugs.gnu.org
Subject: [bug#63296] [PATCH] gnu: Add capnproto-0.9
Date: Thu, 11 May 2023 15:42:25 +0200 [thread overview]
Message-ID: <87ilcz2ddq.fsf@gnu.org> (raw)
In-Reply-To: <4fb8c652-b8dd-4be9-bdf4-7abbc0ed29b0@pantherx.org> (Franz Geffke's message of "Fri, 5 May 2023 11:31:51 +0100")
Hi Franz,
Franz Geffke <franz@pantherx.org> skribis:
> diff --git a/gnu/packages/serialization.scm b/gnu/packages/serialization.scm
> index 39954d6764..d0b44f7709 100644
> --- a/gnu/packages/serialization.scm
> +++ b/gnu/packages/serialization.scm
> @@ -613,6 +613,20 @@ (define-public capnproto
> RPC system. Think JSON, except binary. Or think Protocol Buffers,
> except faster.")
> (license license:expat)))
>
> +(define-public capnproto-0.9
Are there packages in Guix that are going to depend on it?
If not, could you explain briefly why we should have it?
In general, we keep old versions if there’s a package depending on it or
if there’s a strong use case (for example, developers may often work
with different versions of Python, GCC, or LLVM, so we keep several
versions of them).
Ludo’.
prev parent reply other threads:[~2023-05-11 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 10:31 [bug#63296] [PATCH] gnu: Add capnproto-0.9 Franz Geffke
2023-05-11 13:42 ` 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
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=87ilcz2ddq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=63296@debbugs.gnu.org \
--cc=franz@pantherx.org \
/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).