Gentoo Archives: gentoo-dev

From: Torsten Veller <tove@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-util/wxglade: ChangeLog wxglade-0.6.ebuild
Date: Mon, 24 Sep 2007 15:46:33
Message-Id: 20070924142343.TA35c32.tv@veller.net
In Reply to: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-util/wxglade: ChangeLog wxglade-0.6.ebuild by Donnie Berkholz
1 * Donnie Berkholz <dberkholz@g.o>:
2 > On 01:35 Mon 24 Sep , Ryan Hill (dirtyepic) wrote:
3 > > dirtyepic 07/09/24 01:35:38
4 > >
5 > > Modified: ChangeLog
6 > > Added: wxglade-0.6.ebuild
7 > > Log:
8 > > Version bump.
9 > > (Portage version: 2.1.3.9)
10 >
11 > > pkg_postinst() {
12 > > python_mod_optimize "${ROOT}"usr/$(get_libdir)/python*/site-packages/wxglade
13 > > }
14 > >
15 > > pkg_postrm() {
16 > > python_mod_cleanup "${ROOT}"usr/$(get_libdir)/python*/site-packages/wxglade
17 > > }
18
19 What do we expect using an eclass function?
20
21 python_mod_optimize needs the optional argument prefixed with ROOT while
22 python_mod_cleanup adds ROOT for the optional argument itself.
23 So python_mod_cleanup above tries to do some cleaning in ${ROOT}/${ROOT}/...
24
25 Both functions should be used in pkg_{pre,post}install only? I
26 think the eclass should adjust the arguments itself then.
27 What are the conditions for python_mod_optimize for a ROOT!=/
28 build?
29 --
30 .: Torsten | :.
31 --
32 gentoo-dev@g.o mailing list