public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/cucumber-messages] rawhide: Make the -cpp-devel subpackage require json-devel
Date: Tue, 07 Jul 2026 03:48:46 GMT	[thread overview]
Message-ID: <178339612643.1.5556374101343695920.rpms-cucumber-messages-2b4ffbde4a05@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/cucumber-messages
Branch : rawhide
Commit : 2b4ffbde4a0520f01804b8305a98df6ded77c0de
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-07-07T04:47:14+01:00
Stats  : +6/-0 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/cucumber-messages/c/2b4ffbde4a0520f01804b8305a98df6ded77c0de?branch=rawhide

Log:
Make the -cpp-devel subpackage require json-devel

---
diff --git a/cucumber-messages.spec b/cucumber-messages.spec
index 0c6569f..0b538a5 100644
--- a/cucumber-messages.spec
+++ b/cucumber-messages.spec
@@ -74,6 +74,12 @@ This package contains libraries implementing Cucumber Messages for C++.
 Summary:        Development files for using the C++ implementation of Gherkin
 
 Requires:       %{name}-cpp-libs%{?_isa} = %{version}-%{release}
+# This appears in the public API. Formally, dependent packages should also have
+# BuildRequires: json-static, since they will indirectly incorporate the
+# header-only library, although manually tracking such indirect dependencies is
+# relatively impractical in practice.
+# https://docs.fedoraproject.org/en-US/packaging-guidelines/#_packaging_header_only_libraries
+Requires:       json-devel%{?_isa}
 
 %description cpp-devel %{common_description}
 

                 reply	other threads:[~2026-07-07  3:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178339612643.1.5556374101343695920.rpms-cucumber-messages-2b4ffbde4a05@fedoraproject.org \
    --to=code@musicinmybrain.net \
    --cc=git-commits@fedoraproject.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox