RetroSearch Browse

Mon Dec 29 11:12:44 EST 2003 · https://mail.python.org/pipermail/python-dev/2003-December/041457.html

Martin v. Loewis wrote:
> On some installations, installer might be present already,
> but in a too-old version (I use the schema of Installer 2.0).
> In principle, the already-present installer should find out
> that it is too old, and suggest some sort of upgrade.

Following up to myself: If this turns out to be a frequent
problem, we could probably go back to an older installer
scheme - in particular, if we don't want to fight Windows
File Protection (which is only transparently supported
in most recent installer versions).

In the sample installer, I put python24.dll into TARGETDIR,
not into System32Folder. I'd like to keep it that way,
as Microsoft discourages deployment into system32. Of course,
if there is a good reason to install python24.dll into
system32, changing the installer generator to do so would
be only a small effort.

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2003-December/041457.html below:

[Python-Dev] Switching to VC.NET 2003