* Donnie Berkholz <[EMAIL PROTECTED]>: > On 13:25 Fri 12 Oct , Remi Cardona (remi) wrote: > > 1.1 > > dev-python/gnome-python-extras/gnome-python-extras-2.19.1-r1.ebuild > > > > file : > > http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-python/gnome-python-extras/gnome-python-extras-2.19.1-r1.ebuild?rev=1.1&view=markup > > plain: > > http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-python/gnome-python-extras/gnome-python-extras-2.19.1-r1.ebuild?rev=1.1&content-type=text/plain > > > pkg_postinst() { > > python_version > > python_mod_optimize > > "${ROOT}usr/$(get_libdir)/python${PYVER}/site-packages/gtk-2.0" > > } > > > > pkg_postrm() { > > python_version > > python_mod_cleanup > > "${ROOT}usr/$(get_libdir)/python${PYVER}/site-packages/gtk-2.0" > > } > > python_mod_optimize() and python_mod_cleanup() already tag ROOT on,
python_mod_optimize() does not. > so for ROOT != / this is broken. But does python_mod_optimize do anything useful with ROOT !=/ and cross-compilation? What if python versions differ? -- .: Torsten Veller | :. -- [EMAIL PROTECTED] mailing list
