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/rust-oxipng] f44: Some reformatting in Cargo.toml
Date: Sun, 09 Aug 2026 06:10:53 GMT	[thread overview]
Message-ID: <178625585308.1.6229511046278426255.rpms-rust-oxipng-59bd2f8c1368@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/rust-oxipng
            Branch : f44
            Commit : 59bd2f8c13682b820bfe1079e700c277731fcd1a
            Author : Benjamin A. Beasley <code@musicinmybrain.net>
            Date   : 2026-08-09T06:58:03+01:00
            Stats  : +17/-14 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/rust-oxipng/c/59bd2f8c13682b820bfe1079e700c277731fcd1a?branch=f44

            Log:
            Some reformatting in Cargo.toml

[skip changelog]

---
diff --git a/rust2rpm.toml b/rust2rpm.toml
index 29d7569..a77f195 100644
--- a/rust2rpm.toml
+++ b/rust2rpm.toml
@@ -8,21 +8,20 @@ number = 10
 file = "https://github.com/shssoichiro/oxipng/archive/v%{version}/oxipng-%{version}.tar.gz"
 comments = [
     """\
-    We need the GitHub archive, in addition to the .crate from crates.io, \
-    because the crate does not contain the xtask/ directory required for \
-    generating a man page. As noted in \
-    https://github.com/shssoichiro/oxipng/issues/654, there are technical \
-    obstacles to including this in the crate. This source also includes the \
-    tests/ directory, which allows us to run tests.\
-    """,
+We need the GitHub archive, in addition to the .crate from crates.io, because \
+the crate does not contain the xtask/ directory required for generating a man \
+page. As noted in https://github.com/shssoichiro/oxipng/issues/654, there are \
+technical obstacles to including this in the crate. This source also includes \
+the tests/ directory, which allows us to run tests.\
+""",
 ]
 
 [scripts.prep]
 pre = [
     """\
 # Copy in the xtask/ directory from the GitHub archive, required for generating
-# the man page. Remove upstream’s lock file, which we cannot respect. Note
-# that the mangen xtask has its own dependencies, so we must run
+# the man page. Remove upstream’s lock file, which we cannot respect. Note that
+# the mangen xtask has its own dependencies, so we must run
 # %%cargo_generate_buildrequires in the xtask directory if we are to invoke it
 # in the build.
 tar -xzvf '%{SOURCE10}' --strip-components=1 oxipng-%{version}/xtask
@@ -41,15 +40,19 @@ popd >/dev/null\
 
 [scripts.build]
 post = [
-    "# Generate the man page",
-    "%{__cargo} run --manifest-path xtask/Cargo.toml -- mangen",
+    """\
+# Generate the man page
+%{__cargo} run --manifest-path xtask/Cargo.toml -- mangen\
+    """
 ]
 
 [scripts.install]
 post = [
-    "mansrc='target/xtask/mangen/manpages/oxipng.1'",
-    "mandest='%{buildroot}%{_mandir}/man1'",
-    "install -t \"${mandest}\" -D -p -m 0644 \"${mansrc}\"",
+    """\
+mansrc='target/xtask/mangen/manpages/oxipng.1'
+mandest='%{buildroot}%{_mandir}/man1'
+install -t \"${mandest}\" -D -p -m 0644 \"${mansrc}\"\
+    """
 ]
 
 [scripts.check]

                 reply	other threads:[~2026-08-09  6:10 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=178625585308.1.6229511046278426255.rpms-rust-oxipng-59bd2f8c1368@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