[rpms/gherkin] f44: Use various long options

[rpms/gherkin] f44: Use various long options

[Benjamin A. Beasley]

A new commit has been pushed.

Repo   : rpms/gherkin
Branch : f44
Commit : ed8df9b27e5e31339a4c6c0b044b1938a39fd364
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-07-16T10:41:19+01:00
Stats  : +14/-13 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/gherkin/c/ed8df9b27e5e31339a4c6c0b044b1938a39fd364?branch=f44

Log:
Use various long options

---
diff --git a/gherkin.spec b/gherkin.spec
index 0bc16e3..e8dce05 100644
--- a/gherkin.spec
+++ b/gherkin.spec
@@ -157,16 +157,16 @@ Requires:       gherkin-data = %{version}-%{release}
 # with CMake. This is easier than trying to convince make that the targets in
 # question have already been built, which is the strategy we follow for the C++
 # acceptance tests.
-sed -r -i 's/^(\.run:) cli \$\(GHERKIN\)/\1/' c/Makefile
+sed --regexp-extended --in-place 's/^(\.run:) cli \$\(GHERKIN\)/\1/' c/Makefile
 # Python: Fix unversioned python interpreter.
-sed -r -i 's@python -m@%{python3} -m@' python/Makefile
+sed --regexp-extended --in-place 's@python -m@%{python3} -m@' python/Makefile
 # Python: We must work with what we have, and compatibility is quite good in
 # practice.
 %pyproject_patch_dependency uv_build:drop_upper
 
 
 %generate_buildrequires
-%pyproject_buildrequires -d python
+%pyproject_buildrequires --directory python
 
 
 %conf
@@ -193,12 +193,12 @@ pushd cpp
 popd
 
 echo '==== Building Python implementation ===='
-%pyproject_wheel -d python
+%pyproject_wheel --directory python
 
 
 %install
-install -t '%{buildroot}%{_datadir}/gherkin' -D -p -m 0644 \
-    gherkin-languages.json
+install -D --preserve-timestamps --mode=0644 \
+    --target='%{buildroot}%{_datadir}/gherkin' gherkin-languages.json
 
 echo '==== Installing C implementation ===='
 pushd c
@@ -215,13 +215,14 @@ mv '%{buildroot}%{_bindir}/gherkin' '%{buildroot}%{_bindir}/gherkin-cpp'
 
 echo '==== Installing Python implementation ===='
 %pyproject_install
-%pyproject_save_files -l gherkin
-ln -s -f %{buildroot}%{_datadir}/gherkin/gherkin-languages.json \
+%pyproject_save_files --assert-license gherkin
+ln --symbolic --force %{buildroot}%{_datadir}/gherkin/gherkin-languages.json \
     '%{buildroot}%{python3_sitelib}/gherkin/gherkin-languages.json'
 symlinks -c -o '%{buildroot}%{python3_sitelib}/gherkin/gherkin-languages.json'
 
 echo '==== Installing man pages ===='
-install -t '%{buildroot}%{_mandir}/man1' -D -p -m 0644 \
+install -D --preserve-timestamps --mode=0644 \
+    --target='%{buildroot}%{_mandir}/man1' \
     '%{SOURCE10}' '%{SOURCE11}'
 
 
@@ -249,13 +250,13 @@ pushd cpp
 %ctest
 %if %{with acceptance_cpp}
 # Keep make from trying to rebuild the C++ implementation or invoke cmate.
-mkdir -p .built
+mkdir --parents .built
 # While there are GHERKIN/GHERKIN_GENERATE_TOKENS variables in the Makefile,
 # symlinking the already-built command-line tools in ./stage/bin is the easiest
 # way to make sure the acceptance tests can run them.
-mkdir -p 'stage/bin'
-ln -s '%{buildroot}%{_bindir}/gherkin-cpp' 'stage/bin/gherkin'
-ln -s '%{buildroot}%{_bindir}/gherkin-generate-tokens' \
+mkdir --parents 'stage/bin'
+ln --symbolic '%{buildroot}%{_bindir}/gherkin-cpp' 'stage/bin/gherkin'
+ln --symbolic '%{buildroot}%{_bindir}/gherkin-generate-tokens' \
     'stage/bin/gherkin-generate-tokens'
 # The executables need to load libcucumber_gherkin, so we also set
 # LD_LIBRARY_PATH. The acceptance tests are not safe for parallel execution.