New bdist_wininst

(From the readme file:) This is a new release of the distutils windows installer. The known bug (bogus error message when an empty file is extracted) is fixed. Other changes: - The target-compile and target-optimize flags of bdist_wininst are gone. It is no longer possible to compile the python files during installation. - The zlib module is no longer required or used by bdist_wininst. - I moved the decompression/extraction code into a separate file (extract.c). - The installer stub is now compressed by UPX (see http://upx.tsx.org/). This reduces the size of the exe (and thus the overhead of the final installer program) from 40 kB to 16 kB. - The installer displays a more uptodate user wizard-like user interface, also containing a graphic: Just's Python Powered logo. (I could not convince myself to use one of the BeOpen logos). - The installation progress bar now moves correctly. Greg, the zip-file contains complete files, not diffs. When you check it in, note that archive.h, extract.c, install.c, install.rc, README.txt, resource.h, wininst.dsp, wininst.dsw and bdist_wininst.py are text-files in DOS format. PythonPowered.bmp and wininst.exe are binary files and should be checked in with -kb. (I'm not sure if wininst.exe should be checked in at all) Thomas Heller

On 25 August 2000, Thomas Heller said:
This is a new release of the distutils windows installer. The known bug (bogus error message when an empty file is extracted) is fixed.
Great! Just checked it all in. Please "cvs update" and make sure I got everything. I'll also be putting out a new code snapshot in a couple of minutes.
Greg, the zip-file contains complete files, not diffs.
It also contained a bunch of other cruft -- (empty) CVS directories, and bits and pieces of the Distutils source tree. Please be careful to just include your code -- misc/* and distutils/command/bdist_wininst.py. Thanks... Greg -- Greg Ward - just another /P(erl|ython)/ hacker gward@python.net http://starship.python.net/~gward/ A man wrapped up in himself makes a very small package.

On 25 August 2000, Thomas Heller said:
This is a new release of the distutils windows installer. The known bug (bogus error message when an empty file is extracted) is fixed.
Great! Just checked it all in. Please "cvs update" and make sure I got everything. I'll also be putting out a new code snapshot in a couple of minutes. Thanks. Everything seems ok.
Greg, the zip-file contains complete files, not diffs.
It also contained a bunch of other cruft -- (empty) CVS directories, and bits and pieces of the Distutils source tree. Please be careful to just include your code -- misc/* and distutils/command/bdist_wininst.py.
My fault. I created the zip-file with WinZip by zipping the whole distutils source tree, and then deleted everything not related to bdist_wininst. Didn't know (and winzip didn't show it) that all this crap was still included. BTW, what do you think of the changes I made, especially this one: - The target-compile and target-optimize flags of bdist_wininst are gone. It is no longer possible to compile the python files during installation. Thomas

On 28 August 2000, Thomas Heller said:
My fault. I created the zip-file with WinZip by zipping the whole distutils source tree, and then deleted everything not related to bdist_wininst. Didn't know (and winzip didn't show it) that all this crap was still included.
Damn GUIs. I mean, a visual representation of what's in your computer is very nice, but only if it really is a complete representation!
BTW, what do you think of the changes I made, especially this one: - The target-compile and target-optimize flags of bdist_wininst are gone. It is no longer possible to compile the python files during installation.
I assume "installation" here means "final installation on the target host", in which case this seems fine to me. If this means that the Windows installer will now be roughly as big as the RPM, because it includes bytecode files, that doesn't bother me too much. Not as much as the "what could go wrong?" aspect to byte-compiling everything on the end-user's machine. ...hmmm, I just whipped up a wininst installer of the current code, and it doesn't have .pyc files in it. I don't see an option to compile at pseudo-install time, either. Are you just assuming that the normal compile-on-demand approach will work on the target machine? I thought NT had sensible permissions, so that ordinary users couldn't necessarily write to a "system" directory... is Python normally installed so that ordinary users can write to its library directory? Greg -- Greg Ward - Unix geek gward@python.net http://starship.python.net/~gward/ Think honk if you're a telepath.
participants (2)
-
Greg Ward
-
Thomas Heller