From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/python-updater:master commit in: /
Date: Sun, 16 Mar 2014 18:09:44 +0000 (UTC) [thread overview]
Message-ID: <1394992802.2979e0ff26da955476d0846aede7acc4d81c82b9.floppym@gentoo> (raw)
commit: 2979e0ff26da955476d0846aede7acc4d81c82b9
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 16 17:47:50 2014 +0000
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Sun Mar 16 18:00:02 2014 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/python-updater.git;a=commit;h=2979e0ff
Source /lib/gentoo/functions.sh, bug 504130.
---
python-updater.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/python-updater.in b/python-updater.in
index 68c6ead..7fc535d 100644
--- a/python-updater.in
+++ b/python-updater.in
@@ -61,8 +61,8 @@ CHECK_PYTHON_ABIS="1"
CHECK_SHARED_LINKING="1"
CHECK_STATIC_LINKING="1"
-# Load the Gentoo-style info macros, but hack to get around it thinking this is an rc script.
-EBUILD="1" . "@GENTOO_PORTAGE_EPREFIX@"/etc/init.d/functions.sh
+# Load the Gentoo-style info macros
+. "@GENTOO_PORTAGE_EPREFIX@"/lib/gentoo/functions.sh
# Portage variables.
PKG_DBDIR="@GENTOO_PORTAGE_EPREFIX@/var/db/pkg"
next reply other threads:[~2014-03-16 18:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 18:09 Mike Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-10 19:26 [gentoo-commits] proj/python-updater:master commit in: / Mike Gilbert
2015-12-10 19:26 Mike Gilbert
2014-04-07 14:11 Mike Gilbert
2014-04-07 14:11 Mike Gilbert
2014-03-17 3:46 Mike Gilbert
2014-03-16 18:09 Mike Gilbert
2014-03-16 18:09 Mike Gilbert
2014-03-16 18:09 Mike Gilbert
2014-03-12 21:59 Mike Gilbert
2013-03-24 15:30 Mike Gilbert
2013-03-24 15:28 Mike Gilbert
2013-03-24 15:17 Mike Gilbert
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=1394992802.2979e0ff26da955476d0846aede7acc4d81c82b9.floppym@gentoo \
--to=floppym@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