From: "Aaron Swenson" <titanofold@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/pgsql-patches:eselect commit in: /
Date: Tue, 26 Apr 2011 21:46:38 +0000 (UTC) [thread overview]
Message-ID: <c3f0774562030462c13873fb4a1c7ffccb2c4416.titanofold@gentoo> (raw)
commit: c3f0774562030462c13873fb4a1c7ffccb2c4416
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Tue Apr 26 11:09:03 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Tue Apr 26 11:09:03 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=c3f07745
Put double quotes back around '-name' to be consistent with the rest of the
module.
Add trailing slash to source path just to be safe.
---
postgresql.eselect | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/postgresql.eselect b/postgresql.eselect
index ecbe766..7ebbfde 100644
--- a/postgresql.eselect
+++ b/postgresql.eselect
@@ -7,7 +7,7 @@ inherit config multilib
DESCRIPTION="Manage active PostgreSQL client applications and libraries"
MAINTAINER="pgsql-bugs@gentoo.org"
SVN_DATE='$Date: $'
-VERSION="1.0.9"
+VERSION="1.0.10"
# Global Data
B_PATH="${EROOT%/}/usr"
@@ -202,13 +202,13 @@ do_set() {
ln -s "${B_PATH}/${x}/postgresql-${SLOT}/${x}" "${B_PATH}/${x}/postgresql"
echo "${B_PATH}/${x}/postgresql" >> "${E_PATH}"/active.links
# Linker works for files
- linker "${B_PATH}/${x}/postgresql-${SLOT}/${x}" \
- '-name lib*' "${B_PATH}/${x}"
+ linker "${B_PATH}/${x}/postgresql-${SLOT}/${x}/" \
+ "-name lib*" "${B_PATH}/${x}"
fi
done
# Link binaries to /usr/bin/
- linker "${B_PATH}/$(lib_dir)/postgresql-${SLOT}/bin" \
+ linker "${B_PATH}/$(lib_dir)/postgresql-${SLOT}/bin/" \
"-type f" "${B_PATH}/bin"
# Default share path
@@ -324,7 +324,7 @@ do_update() {
done
local tmp_manpath="${B_PATH}/share/postgresql-${curslot}/man/"
[[ -d ${tmp_manpath} ]] && manpath+=":${tmp_manpath}"
- linker "${B_PATH}/$(lib_dir)/postgresql-${curslot}/bin" \
+ linker "${B_PATH}/$(lib_dir)/postgresql-${curslot}/bin/" \
"-type f" "${B_PATH}/bin" "${curslot//.}"
echo "done."
done
next reply other threads:[~2011-04-26 21:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 21:46 Aaron Swenson [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-21 11:38 [gentoo-commits] proj/pgsql-patches:eselect commit in: / Aaron Swenson
2013-11-21 11:19 Aaron Swenson
2013-07-27 21:42 Aaron Swenson
2013-07-27 21:34 Aaron Swenson
2013-07-13 14:06 Aaron Swenson
2013-06-13 10:33 Aaron Swenson
2013-02-08 12:35 Aaron Swenson
2013-02-03 13:35 Aaron Swenson
2012-02-22 11:43 Aaron Swenson
2011-04-26 21:46 Aaron Swenson
2011-04-24 13:18 Aaron Swenson
2011-04-22 10:45 Aaron Swenson
2011-04-22 10:27 Aaron Swenson
2011-04-22 10:08 Aaron Swenson
2011-04-21 23:30 Aaron Swenson
2011-04-21 23:27 Aaron Swenson
2011-04-19 0:45 Aaron Swenson
2011-04-14 11:52 Aaron Swenson
2011-04-02 11:24 Aaron Swenson
2011-04-01 11:51 Aaron Swenson
2011-04-01 11:49 Aaron Swenson
2011-04-01 11:43 Aaron Swenson
2011-04-01 11:14 Aaron Swenson
2011-03-29 19:34 Aaron Swenson
2011-03-29 19:34 Aaron Swenson
2011-03-27 13:28 Aaron Swenson
2011-03-26 2:13 Aaron Swenson
2011-03-24 22:41 Aaron Swenson
2011-03-22 3:07 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=c3f0774562030462c13873fb4a1c7ffccb2c4416.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