public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Maxwell G <maxwell@gtmx.me>
To: git-commits@fedoraproject.org
Subject: [rpms/caddy] rawhide: Use %go_vendor_license_buildrequires instead of static BRs
Date: Thu, 25 Jun 2026 03:43:51 GMT	[thread overview]
Message-ID: <178235903143.1.3452638513705077458.rpms-caddy-eb03c3bdf2a9@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/caddy
            Branch : rawhide
            Commit : eb03c3bdf2a9e32115043f52d84d33245c133a9f
            Author : Maxwell G <maxwell@gtmx.me>
            Date   : 2026-06-22T23:22:23-05:00
            Stats  : +4/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/caddy/c/eb03c3bdf2a9e32115043f52d84d33245c133a9f?branch=rawhide

            Log:
            Use %go_vendor_license_buildrequires instead of static BRs

See
https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/#_installing_go_vendor_tools.
It's preferable to use dynamic BRs instead of statically requiring the
license detector backend's dependencies, since they could change in the
future.

[skip changelog]

---
diff --git a/caddy.spec b/caddy.spec
index 461db00..c9a89eb 100644
--- a/caddy.spec
+++ b/caddy.spec
@@ -27,7 +27,6 @@ Patch1:         0001-Disable-commands-that-can-alter-the-binary.patch
 
 BuildRequires:  go-rpm-macros
 BuildRequires:  go-vendor-tools
-BuildRequires:  askalono-cli
 
 BuildRequires:  systemd-rpm-macros
 %{?systemd_ordering}
@@ -44,6 +43,10 @@ Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS.
 %autosetup -p 1 -a 1
 
 
+%generate_buildrequires
+%go_vendor_license_buildrequires -c %{S:2}
+
+
 %build
 export GO_LDFLAGS="-X github.com/caddyserver/caddy/v2.CustomVersion=v%{version}"
 %gobuild -o bin/caddy ./cmd/caddy

                 reply	other threads:[~2026-06-25  3:43 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=178235903143.1.3452638513705077458.rpms-caddy-eb03c3bdf2a9@fedoraproject.org \
    --to=maxwell@gtmx.me \
    --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