From: David Leverton <levertond@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Major changes to the Gnome2 Eclasses
Date: Fri, 14 Mar 2008 11:52:28 +0000 [thread overview]
Message-ID: <200803141152.29281.levertond@googlemail.com> (raw)
In-Reply-To: <47DA25CF.10205@gentoo.org>
On Friday 14 March 2008 07:14:23 Rémi Cardona wrote:
> - the gnome2 eclass now has a pkg_preinst, if you do multiple
> inherits, make sure that gnome2_pkg_preinst is called too. The
> _games_eclass_ is one of those.
Maybe worth adding a dummy to the current version of the eclass so that
ebuilds can be updated now, instead of suddenly all at once as soon as the
new eclass is committed?
> - if you use functions from the gnome2-utils.eclass, things may not
> work as expected. The _xfce_eclasses_ are on that list.
Are you referring to the need to call gnome2_gconf_savelist in pkg_preinst if
the ebuild/eclass wants to use the gconf functions? What I said above goes
here as well.
A couple of things that aren't specific to the new eclass, but I noticed them
while checking:
> #gnome2_pkg_prerm() {
> # gnome2_gconf_uninstall
> #}
Should this really be commented out? If so, might be worth adding a comment
explaining why - it's not clear whether it's disabled because it's broken, or
not necessary, or whether ebuilds are expected to call gnome2_gconf_uninstall
explicitly if they need to.
> # Path to gconftool-2
> GCONFTOOL_BIN=${GCONFTOOL_BIN:="${ROOT}usr/bin/gconftool-2"}
> # Path to scrollkeeper-update
>
SCROLLKEEPER_UPDATE_BIN=${SCROLLKEEPER_UPDATE_BIN:="${ROOT}usr/bin/scrollkeeper-update"}
Those aren't going to work with cross-compilation (which isn't well-supported
by the current ebuild format, but best to be future-proof), since the
executables in ${ROOT} won't be able to run on the build machine.
> export GCONF_CONFIG_SOURCE=$(${GCONFTOOL_BIN} --get-default-source)
I confess I don't know much about gconf, but that looks as though it'll always
return a path in /, not ${ROOT}, so it'll install the schemas in the /
database.
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-14 11:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 7:14 [gentoo-dev] [RFC] Major changes to the Gnome2 Eclasses Rémi Cardona
2008-03-14 9:09 ` Denis Dupeyron
2008-03-14 10:21 ` Rémi Cardona
2008-03-14 11:34 ` Denis Dupeyron
2008-03-14 11:52 ` David Leverton [this message]
2008-03-14 12:14 ` Petteri Räty
2008-03-14 12:26 ` David Leverton
2008-03-14 12:56 ` Petteri Räty
2008-03-14 12:20 ` Rémi Cardona
2008-03-14 12:58 ` David Leverton
2008-03-14 12:22 ` Petteri Räty
2008-03-17 16:32 ` Rémi Cardona
2008-03-17 17:51 ` Nirbheek Chauhan
2008-03-17 19:57 ` Rémi Cardona
2008-03-17 23:42 ` Gilles Dartiguelongue
2008-03-18 1:06 ` Bo Ørsted Andresen
2008-03-18 6:43 ` Rémi Cardona
2008-03-18 7:06 ` Dawid Węgliński
2008-03-18 0:35 ` Petteri Räty
2008-03-18 6:37 ` Rémi Cardona
2008-03-18 11:33 ` Petteri Räty
2008-03-20 8:23 ` [gentoo-dev] " Steve Long
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=200803141152.29281.levertond@googlemail.com \
--to=levertond@googlemail.com \
--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