From: Mark Wielaard <mark@klomp.org>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: debugedit@sourceware.org
Subject: Re: [PATCH] find-debuginfo.sh: Add --help, --version and man page.
Date: Fri, 30 Apr 2021 14:37:53 +0200 [thread overview]
Message-ID: <1eb6736a4891f2d3858140738a18c5551efd50bd.camel@klomp.org> (raw)
In-Reply-To: <20210430121907.GF5477@altlinux.org>
Hi Dmitry,
On Fri, 2021-04-30 at 15:19 +0300, Dmitry V. Levin wrote:
> It would look even nicer if EOF was quoted, e.g. 'EOF'.
> From bash manual page:
> "If any part of word is quoted, the delimiter is the result of quote
> removal on word, and the lines in the here-document are not
> expanded."
>
> [...]
> > +--unique-debug-src-base \"%{name}-%{VERSION}-
> > %{RELEASE}.%{_arch}\")
>
> I suggest to quote EOF once and forget about quoting anything in the
> whole text.
You are right again, the current escaping looks ugly in the --help
text. I fixed it like you suggested:
diff --git a/scripts/find-debuginfo.sh b/scripts/find-debuginfo.sh
index 5ea57ca..4f7ebef 100755
--- a/scripts/find-debuginfo.sh
+++ b/scripts/find-debuginfo.sh
@@ -19,7 +19,7 @@
help()
{
- cat <<EOF
+ cat <<'EOF'
Usage: find-debuginfo.sh [OPTION]... [builddir]
automagically generates debug info and file lists
@@ -80,17 +80,17 @@ If --build-id-seed SEED is given then debugedit is
called to
update the build-ids it finds adding the SEED as seed to recalculate
the build-id hash. This makes sure the build-ids in the ELF files
are unique between versions and releases of the same package.
-(Use --build-id-seed \"%{VERSION}-%{RELEASE}\".)
+(Use --build-id-seed "%{VERSION}-%{RELEASE}".)
If --unique-debug-suffix SUFFIX is given then the debug files created
for <FILE> will be named <FILE>-<SUFFIX>.debug. This makes sure
.debug
are unique between package version, release and architecture.
-(Use --unique-debug-suffix \"-%{VERSION}-%{RELEASE}.%{_arch}\".)
+(Use --unique-debug-suffix "-%{VERSION}-%{RELEASE}.%{_arch}".)
If --unique-debug-src-base BASE is given then the source directory
will be called /usr/debug/src/<BASE>. This makes sure the debug
source
dirs are unique between package version, release and achitecture (Use
---unique-debug-src-base \"%{name}-%{VERSION}-%{RELEASE}.%{_arch}\")
+--unique-debug-src-base "%{name}-%{VERSION}-%{RELEASE}.%{_arch}")
All file names in switches are relative to builddir ('.' if not
given).
EOF
prev parent reply other threads:[~2021-04-30 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 22:46 Mark Wielaard
2021-04-29 23:06 ` Dmitry V. Levin
2021-04-30 12:10 ` Mark Wielaard
2021-04-30 12:19 ` Dmitry V. Levin
2021-04-30 12:37 ` Mark Wielaard [this message]
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=1eb6736a4891f2d3858140738a18c5551efd50bd.camel@klomp.org \
--to=mark@klomp.org \
--cc=debugedit@sourceware.org \
--cc=ldv@altlinux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).