* Donnie Berkholz <[EMAIL PROTECTED]>:
> On 01:35 Mon 24 Sep , Ryan Hill (dirtyepic) wrote:
> > dirtyepic 07/09/24 01:35:38
> >
> > Modified: ChangeLog
> > Added: wxglade-0.6.ebuild
> > Log:
> > Version bump.
> > (Portage version: 2.1.3.9)
>
> > pkg_postinst() {
> > python_mod_optimize
> > "${ROOT}"usr/$(get_libdir)/python*/site-packages/wxglade
> > }
> >
> > pkg_postrm() {
> > python_mod_cleanup
> > "${ROOT}"usr/$(get_libdir)/python*/site-packages/wxglade
> > }
What do we expect using an eclass function?
python_mod_optimize needs the optional argument prefixed with ROOT while
python_mod_cleanup adds ROOT for the optional argument itself.
So python_mod_cleanup above tries to do some cleaning in ${ROOT}/${ROOT}/...
Both functions should be used in pkg_{pre,post}install only? I
think the eclass should adjust the arguments itself then.
What are the conditions for python_mod_optimize for a ROOT!=/
build?
--
.: Torsten | :.
--
[EMAIL PROTECTED] mailing list
