Christian Heimes [EMAIL PROTECTED] added the comment:
As far as I understood recent commits Martin has figured out how to
integrate the VS CRT redist merge modules into the MSI installer. Am I
correct?
--
status: open - pending
__
Tracker [EMAIL
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Correct. This is now fixed.
--
resolution: - fixed
status: pending - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1569
__
Jeroen Ruigrok van der Werven added the comment:
Hi Martin,
yes, that's exactly what I am saying actually. :)
This is the resulting file I created: Python26.msi
Right now it only installs into C:\Python26 and puts python.exe,
pythonw.exe and python26.dll there, but it is a start.
In
Martin v. Löwis added the comment:
Ok, I never doubted VS can do merge modules (what else if not VS could
do so?). What I'm still questioning that it is possible to do a full
Python installer as a VS setup project. I personally don't think it's
even worth the effort to try, but I might be wrong.
Jeroen Ruigrok van der Werven added the comment:
OK, I played around a bit and created a setup project (.vdproj file).
The relevant part for the merge modules is:
MergeModule
{
{CEE29DC0-9FBA-4B99-8D47-5BC643D9B626}:_8968169979C7478FA06F2A63790836FB
{
Martin v. Löwis added the comment:
So on that front I think it is a mission accomplished, now to tweak and
tune.
Please do attach the project. I can't quite understand what it is that
you have achieved. Is that a project file that can create a full Python
installer?
Jeroen Ruigrok van der Werven added the comment:
As taken from http://blogs.msdn.com/astebner/
archive/2006/08/23/715755.aspx
Hi Didier - You should not try to install this vcredist package using
a nested install. Performing nested installs causes problems with
installing hotfixes for the
Martin v. Löwis added the comment:
asmodai, which details in these postings are you referring to
specifically? I find none of them helpful, wrt to packaging Python.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1569
__
Jeroen Ruigrok van der Werven added the comment:
The hints that the vcredist cannot/should not be installed nested, but
should be chained.
The details on the full flags used/supported by the vcredist files.
And the last one how to do the merge modules (and some other
scenario's) way of adding
New submission from Christian Heimes:
The 3.0a2 installer requires the user to install the VS CRT library
manually. 3.0a3 and 2.6a1 should automate the installation of vsredist
somehow.
--
components: Installation, Windows
keywords: py3k
messages: 58278
nosy: jorend, loewis, tiran
Martin v. Löwis added the comment:
I tried running vcredist from within the python MSI. That aborts with
error message that it can't run another installer while one is already
running.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1569
11 matches
Mail list logo