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/snakemake] f43: Use more long options
Date: Mon, 01 Jun 2026 12:48:18 GMT [thread overview]
Message-ID: <178031809826.1.4590635242880702020.rpms-snakemake-345cc4ca690c@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/snakemake
Branch : f43
Commit : 345cc4ca690cdc482ab165c0f046a73f3696c833
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-05-24T00:11:59+01:00
Stats : +3/-3 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/snakemake/c/345cc4ca690cdc482ab165c0f046a73f3696c833?branch=f43
Log:
Use more long options
---
diff --git a/snakemake.spec b/snakemake.spec
index 8456562..ca92d27 100644
--- a/snakemake.spec
+++ b/snakemake.spec
@@ -485,15 +485,15 @@ sed --regexp-extended --in-place \
# We wait until %%install to generate the man page so that we can use the
# proper script entry point. The generated man page is not perfect, but it is
# good enough to be useful.
-install -d %{buildroot}%{_mandir}/man1
+install --directory %{buildroot}%{_mandir}/man1
PATH="${PATH-}:%{buildroot}%{_bindir}" \
PYTHONPATH='%{buildroot}%{python3_sitelib}' \
help2man --no-info --name='%{summary}' snakemake \
> %{buildroot}%{_mandir}/man1/snakemake.1
# Install nano syntax highlighting
-install -t '%{buildroot}%{_datadir}/nano' -D -m 0644 -p \
- misc/nano/syntax/snakemake.nanorc
+install -D --preserve-timestamps --mode=0644 \
+ --target='%{buildroot}%{_datadir}/nano' misc/nano/syntax/snakemake.nanorc
# Install vim syntax highlighting
install --directory '%{buildroot}%{_datadir}/vim/vimfiles'
reply other threads:[~2026-06-01 12:48 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=178031809826.1.4590635242880702020.rpms-snakemake-345cc4ca690c@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