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/python-uv-build] epel10: Slightly better license-expression formatting in the spec file
Date: Thu, 19 Nov 2026 20:37:54 GMT	[thread overview]
Message-ID: <179512067430.1.1673511503130261108.rpms-python-uv-build-4d4e0ec57963@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-uv-build
            Branch : epel10
            Commit : 4d4e0ec579634eba2dbcb868374139b5ce386842
            Author : Benjamin A. Beasley <code@musicinmybrain.net>
            Date   : 2026-11-19T20:36:49+00:00
            Stats  : +21/-21 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-uv-build/c/4d4e0ec579634eba2dbcb868374139b5ce386842?branch=epel10

            Log:
            Slightly better license-expression formatting in the spec file

[skip changelog]

---
diff --git a/python-uv-build.spec b/python-uv-build.spec
index 0672925..4de2c03 100644
--- a/python-uv-build.spec
+++ b/python-uv-build.spec
@@ -10,7 +10,12 @@ Summary:        The uv build backend
 # Apache-2.0 OR BSD-2-Clause:
 #   - crates/uv-pep440/ is vendored and forked from crate(pep440_rs)
 #   - crates/uv-pep508/ is vendored and forked from crate(pep508_rs)
-#
+%global upstream_license Apache-2.0 OR MIT
+SourceLicense:  (%{upstream_license}) %{shrink:
+    AND (Apache-2.0 OR BSD-2-Clause)
+    AND MPL-2.0
+    }
+License:        %{sourcelicense}
 # Rust crates compiled into the executable contribute additional license terms.
 # To obtain the following list of licenses, build the package and note the
 # output of %%{cargo_license_summary}.
@@ -34,25 +39,20 @@ Summary:        The uv build backend
 # Unicode-3.0
 # Unlicense OR MIT
 # Zlib
-License:        %{shrink:
-    (Apache-2.0 OR MIT) AND
-    (Apache-2.0 OR BSD-2-Clause) AND
-    MPL-2.0
-    }
-%global extra_crate_licenses %{shrink:
-    (0BSD OR Apache-2.0 OR MIT) AND
-    (Apache-2.0 OR Apache-2.0 WITH LLVM-exception OR MIT) AND
-    (Apache-2.0 OR BSD-2-Clause OR MIT) AND
-    (Apache-2.0 OR BSL-1.0) AND
-    (Apache-2.0 OR MIT OR Zlib) AND
-    (Apache-2.0 OR MIT-0) AND
-    BSD-3-Clause AND
-    CC0-1.0 AND
-    MIT AND
-    (MIT OR Unlicense) AND
-    Unicode-3.0 AND
-    Unicode-DFS-2016 AND
-    Zlib
+%global full_license %{sourcelicense} %{shrink:
+    AND (0BSD OR Apache-2.0 OR MIT)
+    AND (Apache-2.0 OR Apache-2.0 WITH LLVM-exception OR MIT)
+    AND (Apache-2.0 OR BSD-2-Clause OR MIT)
+    AND (Apache-2.0 OR BSL-1.0)
+    AND (Apache-2.0 OR MIT OR Zlib)
+    AND (Apache-2.0 OR MIT-0)
+    AND BSD-3-Clause
+    AND CC0-1.0
+    AND MIT
+    AND (MIT OR Unlicense)
+    AND Unicode-3.0
+    AND Unicode-DFS-2016
+    AND Zlib
     }
 URL:            https://pypi.org/project/uv-build
 Source:         %{pypi_source uv_build}
@@ -90,7 +90,7 @@ backend.}
 
 %package -n     python3-uv-build
 Summary:        %{summary}
-License:        %{license} AND %{extra_crate_licenses}
+License:        %{full_license}
 # LICENSE.dependencies contains a full license breakdown
 
 # In https://github.com/astral-sh/uv/issues/5588#issuecomment-2257823242,

                 reply	other threads:[~2026-11-19 20:37 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=179512067430.1.1673511503130261108.rpms-python-uv-build-4d4e0ec57963@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