On Tue, Dec 06, 2005 at 01:22:23PM -0500, Tim Peters wrote:
| [Sidnei]
| Indeed. From reading around, seems like the saner thing is to make it
| a bold warning in the installer that the said dll is required instead
| of shipping it.
|
| [Tim]
| If you go the Zope3-route, it becomes a non-issue:
...
[Sidnei da Silva]
Simplifying a lot what the existing Zope 2 installer does, it
basically creates a 'software home', a default 'instance home' and
registers the services. All but the first part is done manually for
Zope 3, so I can see the lack of glow there.
There's also that Zope2
On Fri, Dec 09, 2005 at 10:19:57PM -0500, Tim Peters wrote:
| Supposing there is a existing python installation, how difficult is it
| to get a distutils-based windows installer to be extracted to a random
| directory outside site-packages?
|
| distutils has no support for that.
|
| My guess
[Sidnei da Silva]
Just noticed a checkin talking about the Windows Installer builder. I
hope to find some time soon to take a look at that, since we now
require Python 2.4 and Python 2.4 uses the 'Microsoft Installer'. I
recall talking with Mark about it and he said it would take some time
to
On Tue, Dec 06, 2005 at 12:35:49PM -0500, Tim Peters wrote:
| [Sidnei da Silva]
| Just noticed a checkin talking about the Windows Installer builder. I
| hope to find some time soon to take a look at that, since we now
| require Python 2.4 and Python 2.4 uses the 'Microsoft Installer'. I
|
...
[Tim]
| Possible headache: Python 2.4.2 requires msvcr71.dll, which is a
| Microsoft DLL (it's akin to msvcrt.dll for Visual Studio 6 -- it's the
| C runtime for VC 7.1), and one for which the redistribution conditions
| are unclear (at least to me). You can't assume that all Windows boxes
