> (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
>> (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
Martin v. Löwis wrote:
>> The Windows builds are hidden in the development section. It took me 10
>> minutes to find them because I was searching in the download section and
>> for nightly builds. The *daily* builds are available at
>> http://www.python.org/dev/daily-msi/
>
> The builds occur 11:00
> The Windows builds are hidden in the development section. It took me 10
> minutes to find them because I was searching in the download section and
> for nightly builds. The *daily* builds are available at
> http://www.python.org/dev/daily-msi/
The builds occur 11:00 UTC (2.5), 12:00 UTC (2.6) 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
> 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
-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
> 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
> 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-3000 mailing list
Python-3000@pyth
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
-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
イェルーン ラ
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
[Barry]
> I'd also like for us to consider doing regular monthly releases.
+1
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archiv
16 matches
Mail list logo
