>> (unless a complete working solution is presented in that other
>> technology, and as long as that other technology still creates MSI
>> files with free-as-in-beer tools).
>
> Just out of interest, what's the reason for enforcing that the
> installer must be an MSI? Or, rather, if I were to pre
> (unless a complete working solution is presented in that other technology,
> and as long as that other technology still creates MSI files with
> free-as-in-beer tools).
Just out of interest, what's the reason for enforcing that the installer must
be an MSI? Or, rather, if I were to present an
> What do you think?
Feel free to try it out. I'm skeptical that it will be a better overall
solution than the current one - the main difference would be that,
rather than me being the only one who can realistically change the
packaging chain, it would be you who is the only one - which, in
prin
>> No, I still haven't found a solution. I do want to use the merge
>> module; anything else probably isn't going to work.
>
> Da...ng
> Didn't you prepare a new MSI installer for 3.0a2 that includes the VS
> Redist MSM for X86? I vaguely remember that you've replaced my installer
> with a new one
> My problem is still getting my head
> around various MSI issues at any level (eg, bdist_msi needs some tweaking to
> allow for different releases of the same "package" to be recognized as such,
> but I'm not sure what MSI concept I'm dealing with yet...)
Don't hesitate to ask here. Not sure what
> Martin v. Löwis wrote:
> > I've looked at it, and I seriously doubt that. In WiX, you need to
> > specify a fixed file list (perhaps with wildcards; I'm unsure). This
> > will be tricky for Python, where the list of files to be installed
> > changes all the time.
> >
> > You *need* to have a turi
Martin v. Löwis wrote:
> I've looked at it, and I seriously doubt that. In WiX, you need to
> specify a fixed file list (perhaps with wildcards; I'm unsure). This
> will be tricky for Python, where the list of files to be installed
> changes all the time.
>
> You *need* to have a turing-complete pa
Martin v. Löwis wrote:
> No, I still haven't found a solution. I do want to use the merge
> module; anything else probably isn't going to work.
Da...ng
Didn't you prepare a new MSI installer for 3.0a2 that includes the VS
Redist MSM for X86? I vaguely remember that you've replaced my installer
wit
-On [20080225 23:03], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>No, I still haven't found a solution. I do want to use the merge
>module; anything else probably isn't going to work.
I updated the ticket with some links to how to approach this issue.
--
Jeroen Ruigrok van der Werven / asmoda
> On the one hand a XML based MSI generator could be easier to maintain.
I've looked at it, and I seriously doubt that. In WiX, you need to
specify a fixed file list (perhaps with wildcards; I'm unsure). This
will be tricky for Python, where the list of files to be installed
changes all the time.
>> For the MSI installers you also need Python 2.5, your pywin32 package
>> and some additional tools like the help compiler and cabarc.exe.
>
> Have you looked at http://wix.sourceforge.net/ ?
Yes.
Martin
___
Python-Dev mailing list
Python-Dev@python
> Have you solved the problem with the VS CRT redist
> (http://bugs.python.org/issue1569)? Maybe Mark is able to assist you.
No, I still haven't found a solution. I do want to use the merge
module; anything else probably isn't going to work.
Regards,
Martin
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 24, 2008, at 1:57 PM, Martin v. Löwis wrote:
>> It very well might. See Christian Heimes's follow up re: Windows
>> builds. OTOH, I'm okay if at least for the alphas, the binary
>> builds lag behind the source releases, though I'd like
Christian Heimes wrote:
> Jeroen Ruigrok van der Werven wrote:
>
>> Have you looked at http://wix.sourceforge.net/ ?
>>
>
> WiX looks interesting but I'm neither in the position to change the
> installer nor do I have a strong opinion. It's Martin's area of expertise.
>
> On the one hand a
Jeroen Ruigrok van der Werven wrote:
> Have you looked at http://wix.sourceforge.net/ ?
WiX looks interesting but I'm neither in the position to change the
installer nor do I have a strong opinion. It's Martin's area of expertise.
On the one hand a XML based MSI generator could be easier to maint
-On [20080225 16:02], Christian Heimes ([EMAIL PROTECTED]) wrote:
>For the MSI installers you also need Python 2.5, your pywin32 package
>and some additional tools like the help compiler and cabarc.exe.
Have you looked at http://wix.sourceforge.net/ ?
--
Jeroen Ruigrok van der Werven / asmodai
Mark Hammond wrote:
> Me too - I still regularly build the svn version of Python, and although I
> don't regularly turn them into .MSI files, I'm confident I could learn how to
> do that ;) I understand that over time the binary process will need some
> tweaking, but in the general case, I expe
Jeroen Ruigrok van der Werven:
> -On [20080224 19:57], "Martin v. Lwis" ([EMAIL PROTECTED]) wrote:
> >I can continue to provide Windows binaries if desired.
>
> If need be, I can help testing the build infrastructure since I have
> access
> to various releases of Visual Studio as well.
Me too - I
-On [20080224 19:57], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>I can continue to provide Windows binaries if desired.
If need be, I can help testing the build infrastructure since I have access
to various releases of Visual Studio as well.
--
Jeroen Ruigrok van der Werven / asmodai
イェルーン ラ
> It very well might. See Christian Heimes's follow up re: Windows
> builds. OTOH, I'm okay if at least for the alphas, the binary builds
> lag behind the source releases, though I'd like to get the process as
> streamlined as possible.
I can continue to provide Windows binaries if desired
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 22, 2008, at 6:54 PM, Brett Cannon wrote:
>> Hi everyone,
>>
>> I've volunteered to be the release manager for Python 2.6 and 3.0.
>> It's been several years since I've RM'd a Python release, and I'm
>> happy to do it again (he says while the m
+1 to everything -- n
On Fri, Feb 22, 2008 at 3:45 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everyone,
>
> I've volunteered to be the release manager for Python 2.6 and 3.0.
> It's been several years since I've RM'd a Python release, a
On Fri, Feb 22, 2008 at 3:45 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everyone,
>
> I've volunteered to be the release manager for Python 2.6 and 3.0.
> It's been several years since I've RM'd a Python release, and I'm
> happy to do i
23 matches
Mail list logo
