all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Nikolay Korotkiy <sikmir@gmail.com>
Cc: 52548@debbugs.gnu.org, Julien Lepiller <julien@lepiller.eu>
Subject: [bug#52548] [PATCH] gnu: Add osmium-tool.
Date: Wed, 05 Jan 2022 23:36:43 +0100	[thread overview]
Message-ID: <875yqxhksk.fsf_-_@gnu.org> (raw)
In-Reply-To: <60396740-64de-b8ac-ec9d-f9d5c24f9627@gmail.com> (Nikolay Korotkiy's message of "Fri, 17 Dec 2021 02:03:13 +0300")

Hi,

Nikolay Korotkiy <sikmir@gmail.com> skribis:

> RapidJSON is header-only library, so it doesn't make much sense to
> unbundle it,

You’re right that it’s different from the situation of .so files.
However, unbundling still clarifies the dependency graph by making code
reuse visible, and it allows us to make sure a security update in
RapidJSON propagates to all its users, should that happen.

> since upstream authors decided to vendor it. And such unbundling could
> complicate maintenance and package expression for no reason. The same
> story about msinttypes, RapidJSON vendors msinttypes.

Yeah it could complicate things, but in some cases it’s a no-brainer.
Could you give it a try and see whether there are any roadblocks?

Thanks in advance,
Ludo’.




  reply	other threads:[~2022-01-05 22:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 11:53 [bug#52548] [PATCH] gnu: Add osmium-tool Nikolay Korotkiy
2021-12-16 11:56 ` [bug#52548] [PATCH] gnu: libosmium: Update to 2.17.2 Nikolay Korotkiy
2021-12-16 22:49 ` [bug#52548] [PATCH] gnu: Add osmium-tool Julien Lepiller
2021-12-16 23:03   ` Nikolay Korotkiy
2022-01-05 22:36     ` Ludovic Courtès [this message]
2022-02-08  8:56 ` Nikolay Korotkiy via Guix-patches via
2022-02-08  9:00 ` [bug#52548] [PATCH 1/2] " Nikolay Korotkiy via Guix-patches via
2022-03-09 22:09   ` bug#52548: [PATCH] " Ludovic Courtès
2022-02-08  9:02 ` [bug#52548] [PATCH] gnu: libosmium: Update to 2.18.0 Nikolay Korotkiy via Guix-patches via

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=875yqxhksk.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=52548@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=sikmir@gmail.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 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.