After update from dev-lang/python-2.7.3-r2 to dev-lang/python-2.7.3-r3 several .exe files are installed: $ file /usr/lib64/python2.7/distutils/command/wininst-*.exe /usr/lib64/python2.7/distutils/command/wininst-6.0.exe: PE32 executable (GUI) Intel 80386, for MS Windows /usr/lib64/python2.7/distutils/command/wininst-7.1.exe: PE32 executable (GUI) Intel 80386, for MS Windows /usr/lib64/python2.7/distutils/command/wininst-8.0.exe: PE32 executable (GUI) Intel 80386, for MS Windows /usr/lib64/python2.7/distutils/command/wininst-9.0-amd64.exe: PE32+ executable (GUI) x86-64, for MS Windows /usr/lib64/python2.7/distutils/command/wininst-9.0.exe: PE32 executable (GUI) Intel 80386, for MS Windows
Hmm, is it possible to use those on Linux somehow (e.g. to build windists)? $ qlist python | grep wininst.*exe /usr/lib64/python2.6/distutils/command/wininst-6.0.exe /usr/lib64/python2.6/distutils/command/wininst-7.1.exe /usr/lib64/python2.6/distutils/command/wininst-8.0.exe /usr/lib64/python2.6/distutils/command/wininst-9.0-amd64.exe /usr/lib64/python2.6/distutils/command/wininst-9.0.exe /usr/lib64/python2.7/distutils/command/wininst-6.0.exe /usr/lib64/python2.7/distutils/command/wininst-7.1.exe /usr/lib64/python2.7/distutils/command/wininst-8.0.exe /usr/lib64/python2.7/distutils/command/wininst-9.0-amd64.exe /usr/lib64/python2.7/distutils/command/wininst-9.0.exe /usr/lib64/pypy1.9/lib-python/2.7/distutils/command/wininst-6.0.exe /usr/lib64/pypy1.9/lib-python/2.7/distutils/command/wininst-7.1.exe /usr/lib64/pypy1.9/lib-python/2.7/distutils/command/wininst-8.0.exe /usr/lib64/pypy1.9/lib-python/2.7/distutils/command/wininst-9.0-amd64.exe /usr/lib64/pypy1.9/lib-python/2.7/distutils/command/wininst-9.0.exe /usr/lib64/pypy2.0/lib-python/2.7/distutils/command/wininst-6.0.exe /usr/lib64/pypy2.0/lib-python/2.7/distutils/command/wininst-7.1.exe /usr/lib64/pypy2.0/lib-python/2.7/distutils/command/wininst-8.0.exe /usr/lib64/pypy2.0/lib-python/2.7/distutils/command/wininst-9.0-amd64.exe /usr/lib64/pypy2.0/lib-python/2.7/distutils/command/wininst-9.0.exe
$ ./setup.py bdist_wininst ... $ ls dist/ flaggie-0.2.linux-x86_64.exe :).
Please make this feature optional, most users will not need it ever.
As Arfrever reminded us, python ebuilds have USE wininst, which is broken now: portage/dev-lang/python $ grep wininst metadata.xml python-2.7.3-r3.ebuild metadata.xml: <flag name="wininst">Install Windows executables required to create an executable installer for MS Windows.</flag> python-2.7.3-r3.ebuild:IUSE="-berkdb build doc elibc_uclibc examples gdbm hardened ipv6 +ncurses +readline sqlite +ssl +threads tk +wide-unicode wininst +xml" python-2.7.3-r3.ebuild: use wininst || rm -f "${libdir})/distutils/command/"wininst-*.exe
You should've mentioned the flag in the first place. Fixed the typo which broke the removal part.