public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Owen W. Taylor <otaylor@fishsoup.net>
To: git-commits@fedoraproject.org
Subject: [flatpaks/flatpak-runtime] f45: Makefile: make the maintainer be more explicit
Date: Fri, 11 Sep 2026 14:40:13 GMT	[thread overview]
Message-ID: <178913761340.1.4530128382186618932.flatpaks-flatpak-runtime-555eadca6baf@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : flatpaks/flatpak-runtime
            Branch : f45
            Commit : 555eadca6baf528093bf22d4496dc468e3151f11
            Author : Owen W. Taylor <otaylor@fishsoup.net>
            Date   : 2018-01-31T11:21:01+01:00
            Stats  : +15/-7 in 3 file(s)
            URL    : https://src.fedoraproject.org/flatpaks/flatpak-runtime/c/555eadca6baf528093bf22d4496dc468e3151f11?branch=f45

            Log:
            Makefile: make the maintainer be more explicit

Instead of having 'make' generate a HTML report and also update
flatpak-runtime.yaml, have a pair of 'make report' and 'make update'.

---
diff --git a/.gitignore b/.gitignore
index 73d7763..eb809d7 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1,4 @@
 out/*
-cache/*
 report.html
-tools/__pycache__
\ No newline at end of file
+tools/__pycache__
+flatpak-runtime.new.yaml

diff --git a/Makefile b/Makefile
index 65b8cc2..f915d6a 100644
--- a/Makefile
+++ b/Makefile
@@ -13,7 +13,15 @@ PROFILE_FILES =					\
 FILE_LISTS = \
           $(patsubst %.packages,%.files,$(PACKAGE_LISTS))
 
-all: report.html flatpak-runtime.yaml
+all:
+	@echo "Targets:"
+	@echo "  report: Generates report.html, and a candidate flatpak-runtime.new.yaml"
+	@echo "  update: Generates the above files, then copies flatpak-runtime.new.yaml to flatpak-runtime.yaml"
+
+report: report.html flatpak-runtime.new.yaml
+
+update: report
+	cp flatpak-runtime.new.yaml flatpak-runtime.yaml
 
 report.html $(PROFILE_FILES): $(PACKAGE_LISTS) package-notes.txt tools/generate-report.py report-template.html
 	./tools/generate-report.py
@@ -27,10 +35,10 @@ $(PACKAGE_LISTS): tools/resolve-files.py $(FILE_LISTS)
 		./tools/resolve-files.py $$f ;		\
 	done
 
-flatpak-runtime.yaml: $(PROFILE_FILES) flatpak-runtime.in.yaml tools/generate-modulemd.py
+flatpak-runtime.new.yaml: $(PROFILE_FILES) flatpak-runtime.in.yaml tools/generate-modulemd.py
 	./tools/generate-modulemd.py
 
 clean:
-	rm -f out/*
+	rm -f out/* report.html flatpak-runtime.new.yaml
 
-.PHONY: clean
+.PHONY: all clean report update

diff --git a/tools/generate-modulemd.py b/tools/generate-modulemd.py
index b3bb4ef..4d9046e 100755
--- a/tools/generate-modulemd.py
+++ b/tools/generate-modulemd.py
@@ -16,5 +16,5 @@ set_profile('runtime-base', 'out/runtime-base.profile')
 set_profile('sdk', 'out/sdk.profile')
 set_profile('sdk-base', 'out/sdk-base.profile')
 
-with open('flatpak-runtime.yaml', 'w') as f:
+with open('flatpak-runtime.new.yaml', 'w') as f:
     ordered_dump(modulemd, stream=f, default_flow_style=False, encoding="utf-8")

                 reply	other threads:[~2026-09-11 14:40 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=178913761340.1.4530128382186618932.flatpaks-flatpak-runtime-555eadca6baf@fedoraproject.org \
    --to=otaylor@fishsoup.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