From: "Rémi Cardona" <remi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Major changes to the Gnome2 Eclasses
Date: Mon, 17 Mar 2008 17:32:48 +0100 [thread overview]
Message-ID: <47DE9D30.7060107@gentoo.org> (raw)
In-Reply-To: <47DA25CF.10205@gentoo.org>
Hi again,
I've just come up with a plan for the new eclass based on previous
feedback. Basically, I want to commit this patch [1] ASAP.
If I commit this right now here's what's going to happen :
- ebuilds that use the gnome2 eclass and other eclasses that don't
export pkg_preinst() will be fine. Most Gnome packages are thus fine.
- ebuilds that have "inherit gnome2 $eclass_foo" [*] will still work
for now, but won't work once I commit the rest of the eclass changes
- ebuilds that have "inherit $eclass_foo gnome2" [*] won't work as
they used to.
[*] if $eclass_foo has indeed a pkg_preinst somewhere, like the games
eclass.
Now, basically, if the portage metadata or QA people could tell me a way
to figure *all* the ebuilds that inherit gnome2 *and* have a
pkg_preinst() function somewhere (either in the ebuild or in an eclass
somewhere) I'd really appreciate it, as I really don't want to read
through thousands of ebuilds to figure it out.
Thanks
Rémi
[1] The Patch (tm)
--- gnome2.eclass 10 Feb 2008 14:47:14 -0000 1.83
+++ gnome2.eclass 17 Mar 2008 16:30:31 -0000
@@ -106,6 +106,9 @@
rm -fr "${D}/usr/share/applications/mimeinfo.cache"
}
+gnome2_pkg_preinst() {
+}
+
gnome2_pkg_postinst() {
gnome2_gconf_install
fdo-mime_desktop_database_update
@@ -131,4 +134,4 @@
fi
}
-EXPORT_FUNCTIONS src_unpack src_compile src_install pkg_postinst pkg_postrm
+EXPORT_FUNCTIONS src_unpack src_compile src_install pkg_preinst
pkg_postinst pkg_postrm
--
Rémi Cardona
LRI, INRIA
remi.cardona@lri.fr
remi@gentoo.org
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-17 16:42 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
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 [this message]
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=47DE9D30.7060107@gentoo.org \
--to=remi@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