i have a problem with the bdist_wininst target for one of my projects.
on Unix (where i use sdist), i override the install command class to
do some customisation and configuration on the destination machine,
but with bdist_wininst, the install command is run on the packager's
machine, not the target.
i'd like to be able to register COM servers, create start-menu
shortcuts, etc, from within the installer.
what do people think about allowing an additional option in the
setup.cfg, understood by bdist_wininst (and, more particularly,
wininst.exe) that is the name of a script to be run by the selected
interpreter after completing the installation?
i could then install a `post_wininst.py' script, add it setup.cfg, and
when run from wininst.exe, it could do the post-installation things, and
if necessary, even remove itself when done. when the script exits,
wininst.exe can splash the final wizard pane, and exit.