From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-plugins/vdr-vdrmanager/
Date: Wed, 15 Aug 2018 07:31:06 +0000 (UTC) [thread overview]
Message-ID: <1534318253.6120cd42a749a0872d22eb15cbc09fe98f92723e.mgorny@gentoo> (raw)
commit: 6120cd42a749a0872d22eb15cbc09fe98f92723e
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 8 21:15:24 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Aug 15 07:30:53 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6120cd42
media-plugins/vdr-vdrmanager: Replace unnecessary path_exists call
Replace the unnecessary path_exists calls with plain bash -f test.
The path_exists function was only intended to be used when necessary
to deal with wildcards.
Closes: https://bugs.gentoo.org/662178
media-plugins/vdr-vdrmanager/vdr-vdrmanager-0.14.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-plugins/vdr-vdrmanager/vdr-vdrmanager-0.14.ebuild b/media-plugins/vdr-vdrmanager/vdr-vdrmanager-0.14.ebuild
index 8639a6df48d..6f324f6bcdc 100644
--- a/media-plugins/vdr-vdrmanager/vdr-vdrmanager-0.14.ebuild
+++ b/media-plugins/vdr-vdrmanager/vdr-vdrmanager-0.14.ebuild
@@ -63,7 +63,7 @@ pkg_postinst() {
einfo "Add a password to /etc/conf.d/vdr.vdrmanager"
if use ssl ; then
- if path_exists -a "${ROOT}${VDRMANAGER_SSL_KEY_FILE}.pem"; then
+ if [[ -f ${ROOT}${VDRMANAGER_SSL_KEY_FILE}.pem ]]; then
einfo "found an existing SSL cert, to create a new SSL cert, run:\n"
einfo "emerge --config ${PN}"
else
next reply other threads:[~2018-08-15 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 7:31 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 19:59 [gentoo-commits] repo/gentoo:master commit in: media-plugins/vdr-vdrmanager/ Ulrich Müller
2021-06-03 19:15 Sam James
2018-07-11 11:47 Tony Vroon
2016-06-24 10:42 Joerg Bornkessel
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=1534318253.6120cd42a749a0872d22eb15cbc09fe98f92723e.mgorny@gentoo \
--to=mgorny@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