Installing dev-libs/Ice-3.4.0 on my ~amd64 using portage 2.2_rc67, I get a long list of error messages from postinst: /Glacier2.py does not exist! ... /Ice.py does not exist! ... /IceStorm does not exist! I'm not sure where this comes from. The fact that the ebuild temporarily overrides EAPI might have something to do with it. The saved environment indicates that the PYTHON_MODULES array does not contain any slashes, so I don't understand where the slashes in the error messages come from.
With the patch from bug #312133 comment #5 the problem mostly goes away. The only error message that remains is this: 'Glacier2' does not exist! Which makes sense, as there really is no directory of that name installed by the ebuild. The ebuild adds that item manually to its PYTHON_MODULES array, and probably that step is wrong. I really hope that all this ugly postinst/postrm hacking for python modules will vanish one day, to be replaced by simple building of these files in the src_compile phase, and proper timestamp preservation as guaranteed by EAPI=3.
(In reply to comment #1) > I really hope that all this ugly postinst/postrm hacking for python modules > will vanish one day, to be replaced by simple building of these files in the > src_compile phase, and proper timestamp preservation as guaranteed by EAPI=3. It's not planned. See bug #301915.
Done, thanks.
