From: "Aaron Swenson" <titanofold@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/postgresql/eselect:master commit in: /
Date: Fri, 19 May 2017 14:20:02 +0000 (UTC) [thread overview]
Message-ID: <1495203028.f2de7834a881e387b7d26978848d754ee56b1e07.titanofold@gentoo> (raw)
commit: f2de7834a881e387b7d26978848d754ee56b1e07
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Fri May 19 14:10:28 2017 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Fri May 19 14:10:28 2017 +0000
URL: https://gitweb.gentoo.org/proj/postgresql/eselect.git/commit/?id=f2de7834
Add support for FEATURES="noman"
In such case the user enabled FEATURES="noman" on Portage, there won’t
be a manpage directory to link to. The module now checks that the
directory exists before trying to use it.
postgresql.eselect | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/postgresql.eselect b/postgresql.eselect
index d7229e5..db669cc 100644
--- a/postgresql.eselect
+++ b/postgresql.eselect
@@ -256,7 +256,11 @@ do_set() {
local mandir mansec
for mandir in "${USR_PATH}"/share/postgresql-${slot}/man/man{1,3,7} ; do
mansec=$(basename "${mandir}")
- linker "${mandir}" "" "${USR_PATH}/share/man/${mansec}"
+ # Because the user could have FEATURES="noman", check the directory
+ # exists before using it. (https://bugs.gentoo.org/618294)
+ if [[ -d ${USR_PATH}/share/man/${mansec} ]] ; then
+ linker "${mandir}" "" "${USR_PATH}/share/man/${mansec}"
+ fi
done
# Default share path - use a relative link here by just specifying the
next reply other threads:[~2017-05-19 14:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 14:20 Aaron Swenson [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-21 11:00 [gentoo-commits] proj/postgresql/eselect:master commit in: / Aaron Swenson
2018-10-21 11:00 Aaron Swenson
2018-01-14 16:43 Aaron Swenson
2018-01-14 16:39 Aaron Swenson
2018-01-14 16:38 Aaron Swenson
2018-01-14 16:28 Aaron Swenson
2018-01-14 16:19 Aaron Swenson
2018-01-14 16:19 Aaron Swenson
2018-01-14 16:19 Aaron Swenson
2017-07-21 18:49 Aaron Swenson
2017-07-21 18:36 Aaron Swenson
2017-05-19 14:24 Aaron Swenson
2017-05-19 14:20 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 Aaron Swenson
2017-04-18 19:43 [gentoo-commits] proj/postgresql/eselect:stateless " Aaron Swenson
2017-04-18 19:43 ` [gentoo-commits] proj/postgresql/eselect:master " Aaron Swenson
2017-02-06 13:19 [gentoo-commits] proj/postgresql/eselect:stateless " Aaron Swenson
2017-04-18 19:43 ` [gentoo-commits] proj/postgresql/eselect:master " Aaron Swenson
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=1495203028.f2de7834a881e387b7d26978848d754ee56b1e07.titanofold@gentoo \
--to=titanofold@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