From: "Arun Raghavan (ford_prefect)" <ford_prefect@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in eclass: gnome2.eclass
Date: Wed, 24 Aug 2011 07:12:35 +0000 (UTC) [thread overview]
Message-ID: <20110824071235.64ADD2004C@flycatcher.gentoo.org> (raw)
ford_prefect 11/08/24 07:12:35
Modified: gnome2.eclass
Log:
Move GST_REGISTRY export to src_prepare
We might end up calling gst functions anywhere (gupnp-dlna calls it in
documentation generation, for example).
Revision Changes Path
1.100 eclass/gnome2.eclass
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/gnome2.eclass?rev=1.100&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/gnome2.eclass?rev=1.100&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/gnome2.eclass?r1=1.99&r2=1.100
Index: gnome2.eclass
===================================================================
RCS file: /var/cvsroot/gentoo-x86/eclass/gnome2.eclass,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -r1.99 -r1.100
--- gnome2.eclass 14 Aug 2011 03:46:33 -0000 1.99
+++ gnome2.eclass 24 Aug 2011 07:12:35 -0000 1.100
@@ -1,6 +1,6 @@
# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/eclass/gnome2.eclass,v 1.99 2011/08/14 03:46:33 nirbheek Exp $
+# $Header: /var/cvsroot/gentoo-x86/eclass/gnome2.eclass,v 1.100 2011/08/24 07:12:35 ford_prefect Exp $
# @ECLASS: gnome2.eclass
# @MAINTAINER:
@@ -85,8 +85,12 @@
# @FUNCTION: gnome2_src_prepare
# @DESCRIPTION:
-# Fix build of scrollkeeper documentation and run elibtoolize.
+# Prepare environment for build, fix build of scrollkeeper documentation,
+# run elibtoolize.
gnome2_src_prepare() {
+ # GST_REGISTRY is to work around gst utilities trying to read/write /root
+ export GST_REGISTRY="${S}/registry.xml"
+
# Prevent scrollkeeper access violations
gnome2_omf_fix
@@ -119,8 +123,7 @@
# Avoid sandbox violations caused by gnome-vfs (bug #128289 and #345659)
addwrite "$(unset HOME; echo ~)/.gnome2"
- # GST_REGISTRY is to work around gst-inspect trying to read/write /root
- GST_REGISTRY="${S}/registry.xml" econf "$@" ${G2CONF}
+ econf "$@" ${G2CONF}
}
# @FUNCTION: gnome2_src_compile
next reply other threads:[~2011-08-24 7:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 7:12 Arun Raghavan (ford_prefect) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-23 19:31 [gentoo-commits] gentoo-x86 commit in eclass: gnome2.eclass Mike Frysinger (vapier)
2012-12-05 23:41 Doug Goldstein (cardoe)
2011-09-25 15:15 Pacho Ramos (pacho)
2011-08-25 18:08 Nirbheek Chauhan (nirbheek)
2011-08-14 3:46 Nirbheek Chauhan (nirbheek)
2011-07-15 17:31 Zac Medico (zmedico)
2011-04-22 11:04 Nirbheek Chauhan (nirbheek)
2011-04-21 21:27 Gilles Dartiguelongue (eva)
2011-04-21 21:06 Gilles Dartiguelongue (eva)
2011-04-21 20:58 Gilles Dartiguelongue (eva)
2011-04-09 13:14 Gilles Dartiguelongue (eva)
2010-12-07 6:20 Gilles Dartiguelongue (eva)
2010-12-07 6:19 Gilles Dartiguelongue (eva)
2010-04-26 19:37 Jonathan Callen (abcd)
2009-02-17 16:05 Daniel Gryniewicz (dang)
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=20110824071235.64ADD2004C@flycatcher.gentoo.org \
--to=ford_prefect@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