public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michal Schorm <mschorm@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-xapp] rawhide: Move BuildRequires to main package section
Date: Sat, 25 Jul 2026 18:01:20 GMT	[thread overview]
Message-ID: <178500248087.1.14975530547032883050.rpms-python-xapp-010fae08bb4f@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-xapp
            Branch : rawhide
            Commit : 010fae08bb4ff5a05589c426787803f34204ff4b
            Author : Michal Schorm <mschorm@redhat.com>
            Date   : 2026-07-25T15:56:07+02:00
            Stats  : +2/-3 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-xapp/c/010fae08bb4ff5a05589c426787803f34204ff4b?branch=rawhide

            Log:
            Move BuildRequires to main package section

Move 'meson' and 'python3-rpm-macros' from the '%package -n
python3-xapp' subpackage section to the main package header.
BuildRequires belong under the source package, not under %package
(which is for subpackage metadata). RPM processes them correctly
either way, but the main header is the conventional location per
Fedora Packaging Guidelines.

No 'python3-devel' is needed: this is a pure-Python package —
'meson.build' uses only 'pymod.find_installation()' and
'install_sources()' (pure file copies, no C compilation, no
'extension_module()'). The '%{python3_sitelib}' macro comes from
'python3-rpm-macros', which is already a BuildRequires.

Linux Mint divergence: LM uses 'python3-all' (a Debian equivalent
that includes development headers) instead of 'python3-devel'.

Upstream references:
- Python module import and find_installation(): https://github.com/linuxmint/python-xapp/blob/3.0.3/meson.build#L3-L4

Co-Authored-By: Claude AI <noreply@anthropic.com>

---
diff --git a/python-xapp.spec b/python-xapp.spec
index d49fef2..1edf0c3 100644
--- a/python-xapp.spec
+++ b/python-xapp.spec
@@ -9,6 +9,8 @@ Source0:        %{url}/archive/%{version}/%{name}-%{version}.tar.gz
 
 BuildArch:      noarch
 BuildRequires:  gettext
+BuildRequires:  meson
+BuildRequires:  python3-rpm-macros
 
 %description
 %{summary}.
@@ -17,9 +19,6 @@ BuildRequires:  gettext
 %package -n python3-xapp
 Summary:       %{summary}
 
-BuildRequires: meson
-BuildRequires: python3-rpm-macros
-
 Requires:      gtk3
 Requires:      python3-gobject-base
 Requires:      python3-psutil

                 reply	other threads:[~2026-07-25 18:01 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=178500248087.1.14975530547032883050.rpms-python-xapp-010fae08bb4f@fedoraproject.org \
    --to=mschorm@redhat.com \
    --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