From: "Patrick McLean" <chutzpah@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/netifrc:master commit in: init.d/
Date: Wed, 31 Mar 2021 01:11:08 +0000 (UTC) [thread overview]
Message-ID: <1617153048.bef5edf9d2d1fcd982ae19a7cb05dc2d58b854e7.chutzpah@OpenRC> (raw)
commit: bef5edf9d2d1fcd982ae19a7cb05dc2d58b854e7
Author: Patrick McLean <chutzpah <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 31 01:06:31 2021 +0000
Commit: Patrick McLean <chutzpah <AT> gentoo <DOT> org>
CommitDate: Wed Mar 31 01:10:48 2021 +0000
URL: https://gitweb.gentoo.org/proj/netifrc.git/commit/?id=bef5edf9
net.lo.in: quote variables in _configure_variables
The variables being passed to eval aren't quoted either in the before-eval
scope, or in what is passed to eval. Make sure they are quoted.
Signed-off-by: Patrick McLean <chutzpah <AT> gentoo.org>
init.d/net.lo.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/init.d/net.lo.in b/init.d/net.lo.in
index 06304e1..0bb69f3 100644
--- a/init.d/net.lo.in
+++ b/init.d/net.lo.in
@@ -225,9 +225,9 @@ _configure_variables()
for var in ${_config_vars}; do
local v=
for t; do
- eval v=\$${var}_${t}
+ eval v="\"\$${var}_${t}\""
if [ -n "${v}" ]; then
- eval ${var}_${IFVAR}=\$${var}_${t}
+ eval "${var}_${IFVAR}=\"\$${var}_${t}\""
continue 2
fi
done
next reply other threads:[~2021-03-31 1:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 1:11 Patrick McLean [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-07 9:42 [gentoo-commits] proj/netifrc:master commit in: init.d/ Sam James
2020-09-07 13:03 Lars Wendler
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2017-11-14 20:48 Robin H. Johnson
2017-11-14 20:48 Robin H. Johnson
2016-10-24 20:52 Robin H. Johnson
2016-10-24 0:23 Robin H. Johnson
2016-10-24 0:23 Robin H. Johnson
2016-10-23 23:50 Robin H. Johnson
2016-07-05 18:13 Robin H. Johnson
2015-11-08 14:30 Robin H. Johnson
2015-11-08 14:30 Robin H. Johnson
2015-05-25 10:04 Mike Frysinger
2015-05-25 10:01 Mike Frysinger
2015-01-09 17:17 Robin H. Johnson
2014-10-11 19:47 Robin H. Johnson
2014-07-17 17:56 Robin H. Johnson
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=1617153048.bef5edf9d2d1fcd982ae19a7cb05dc2d58b854e7.chutzpah@OpenRC \
--to=chutzpah@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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