> 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" >> }
While you guys are on this subject, I thought I would put in the experience I just had. http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-java/java-config/java-config-2.1.2.ebuild?rev=1.1&view=markup As you will note in the ebuild above I inherit distutils and then declare PYTHON_MODNAME="java_config_2" and have my 2 functions as so.... pkg_postrm() { distutils_python_version distutils_pkg_postrm } pkg_postinst() { distutils_pkg_postinst ... ... } Firstly it is interesting to note that you must call *python_version before distutils_pkg_postrm while distutils_pkg_postinst handles this itself. Is this a good solution? Would it also be a good solution in your case? PYTHON_MODNAME from my understanding what i've investigated will accept a list of modules if you need it to. Anyway, hopefully this helps. Alistair. ps. My python experience has not left the realm of java-config and I have only done 2 releases, 1 1/2 of which I completely screwed up. I am no expert and have no idea whether the above is correct, valid or otherwise safe for human consumption. Don't complain!! -- [EMAIL PROTECTED] mailing list
