From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/crossdev:master commit in: wrappers/
Date: Tue, 18 Oct 2011 17:36:13 +0000 (UTC) [thread overview]
Message-ID: <f4d0c96ff5510f0b70219fb634d354b694741891.vapier@gentoo> (raw)
commit: f4d0c96ff5510f0b70219fb634d354b694741891
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 12 21:30:00 2011 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Wed Oct 12 21:32:13 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/crossdev.git;a=commit;h=f4d0c96f
cross-emerge: optimize/fix portageq usage
Only execute portageq once to speed things up, and only remove the
variables we are looking up from the env. Using the -i flag makes
portage very unhappy when $PATH goes missing.
Signed-off-by: Mike Frysinger <vapier <AT> gentoo.org>
---
wrappers/cross-emerge | 14 +++++++++-----
1 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/wrappers/cross-emerge b/wrappers/cross-emerge
index 85f847d..7af770b 100755
--- a/wrappers/cross-emerge
+++ b/wrappers/cross-emerge
@@ -1,5 +1,5 @@
#!/bin/sh
-# Copyright 2008-2010 Gentoo Foundation
+# Copyright 2008-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
if [ -z "${CHOST}" ] ; then
@@ -20,10 +20,14 @@ fi
# Portage defaults CBUILD to CHOST, so we have to remove CHOST
# from the env to get a "good" value for CBUILD
-: ${CBUILD=$(env -i portageq envvar CBUILD)}
-: ${BUILD_CFLAGS=$(env -i portageq envvar CFLAGS)}
-: ${BUILD_CXXFLAGS=$(env -i portageq envvar CXXFLAGS)}
-: ${BUILD_CPPFLAGS=$(env -i portageq envvar CPPFLAGS)}
+query_vars="CBUILD CFLAGS CXXFLAGS CPPFLAGS"
+clean_vars="${query_vars} CHOST SYSROOT PORTAGE_CONFIGROOT"
+eval $(env $(printf -- '-u %s ' ${clean_vars}) \
+ portageq envvar -v ${query_vars} | sed s:^:_E_:)
+: ${CBUILD=${_E_CBUILD}}
+: ${BUILD_CFLAGS=${_E_CFLAGS}}
+: ${BUILD_CXXFLAGS=${_E_CXXFLAGS}}
+: ${BUILD_CPPFLAGS=${_E_CPPFLAGS}}
export CBUILD BUILD_CFLAGS BUILD_CXXFLAGS BUILD_CPPFLAGS
FAKEROOT=
next reply other threads:[~2011-10-18 17:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 17:36 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-27 23:13 [gentoo-commits] proj/crossdev:master commit in: wrappers/ Mike Frysinger
2013-01-28 22:51 Mike Frysinger
2013-12-23 3:06 Mike Frysinger
2014-01-18 19:37 Mike Frysinger
2014-03-27 6:43 Mike Frysinger
2014-09-17 21:41 Mike Frysinger
2014-07-29 6:07 ` Mike Frysinger
2014-09-17 21:41 Mike Frysinger
2014-07-29 6:07 ` Mike Frysinger
2014-09-17 21:41 Mike Frysinger
2014-09-18 16:52 Mike Frysinger
2014-10-31 0:52 Mike Frysinger
2014-10-31 1:56 Mike Frysinger
2014-10-31 1:56 Mike Frysinger
2015-07-23 3:47 Mike Frysinger
2016-01-16 8:22 Mike Frysinger
2017-12-30 17:45 Sergei Trofimovich
2017-12-30 22:37 Sergei Trofimovich
2018-03-10 13:07 Sergei Trofimovich
2018-03-24 15:13 Sergei Trofimovich
2018-04-05 6:56 Sergei Trofimovich
2018-10-20 20:08 Sergei Trofimovich
2019-03-11 22:13 Sergei Trofimovich
2019-03-18 22:54 Sergei Trofimovich
2019-07-12 7:24 Sergei Trofimovich
2019-07-21 13:41 James Le Cuirot
2019-08-30 7:32 Sergei Trofimovich
2021-01-17 8:09 Sergei Trofimovich
2021-06-21 21:23 Sergei Trofimovich
2021-10-27 8:55 Mike Frysinger
2021-11-26 19:02 Mike Frysinger
2022-01-13 8:20 Mike Frysinger
2022-01-13 8:20 Mike Frysinger
2022-08-18 21:57 Sam James
2022-08-18 21:57 Sam James
2022-12-27 16:06 Sam James
2023-06-16 20:21 Mike Gilbert
2023-09-23 12:56 Sam James
2023-10-15 4:23 Matt Turner
2024-01-08 14:28 Sam James
2024-05-04 11:58 Sam James
2024-09-22 8:35 James Le Cuirot
2024-11-30 2:08 Sam James
2025-01-29 17:42 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=f4d0c96ff5510f0b70219fb634d354b694741891.vapier@gentoo \
--to=vapier@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