The ebuild of =games-engines/renpy-6.14.1-r1 calls einfo "running: eselect renpy update --if-unset" eselect renpy update --if-unset before the installation-stage, i.e. even on first installation. This of course has to fail as the files are not yet there. Output can be seen in the attached build-log. I think moving the line to post-install should be sufficient. As a workaround, calling "eselect renpy update --if-unset" manually after installation works fine, too. Reproducible: Always Steps to Reproduce: 1. Emerge =games-engines/renpy-6.14.1-r1 on a system with no renpy installed before. 2. Check with eselect renpy list which renpy version is selected. Actual Results: No renpy-version is selected at all. Expected Results: Select the new freshly installed renpy-version.
Created attachment 341798 [details] Build+install log of =games-engines:renpy-6.14.1-r1 with the eselect-error Look for the line "!!! Error: No targets for //usr/games/bin/renpy, system likely broken." at begin of install stage.
Yes, shouldn't that be called in pkg_postinst() instead?
right, thanks for report, also added it to pkg_postrm + 13 Mar 2013; Julian Ospald <hasufell@gentoo.org> renpy-6.14.1-r1.ebuild, + renpy-6.15.0.ebuild: + fix eselect logic wrt #461518 no revbump since I consider this trivial
