> Can you please cite a source for that recommendation? Preferably
> some MSDN documentation.
http://msdn.microsoft.com/en-us/library/aa368269(v=vs.85).aspx
http://wix.sourceforge.net/manual-wix3/add_a_file.htm
Specifically, starting in bold, where it says "In general, you should restrict
yours
> At work we keep the required stable UUIDs in an ConfigParser-format
> file checked in to the VCS for that purpose.
>
> FWIW our build system uses WiX (v2) currently and if I where to redo
> it, I'd change to msilib and not WiX v3. But never change working
> systems.
No need to do that if you're
> I hadn't thought it through fully, but the preceding paragraph really
> gets to the core of the problem. The maintenance nightmare is security
> updates for private location installations by third parties. The only
> MSI-friendly way to update that code is through releasing an updated
> merge mod
> I found it much easier to use than WiX, which I also tried.
I also used to use the Visual Studio installer projects until I needed
something a lot more robust (e.g., customized UI + localizable strings). msilib
does the job people need it to do and that's fine. I'm really not trying to
argue
> If Python was starting at ground zero, and the choices were to create
> a library or to use WiX, the answer might have been different.
> However with a mature enough library to suit all the needs that anyone
> has been willing to author, it's certainly more work to create the WiX
> install and
> Using msilib is easier than using Wix. It's also more flexible.
IMO, no. It's simply not.
> All you have to know is how the MSI schema works.
Same with WiX.
> It could easily be extended to do so, in a straight-forward manner.
Other packaging apps already have it - no work needed.
> (actual
>> Is there or will there be support for python merge modules so we can
>> include python in our installer?
>
>I haven't planned any. Contributions are welcome.
>
>> But has there been thought towards migrating away from msilib and using
>> platform standard tools such as wix (used by ms office, vi
Is there or will there be support for python merge modules so we can include
python in our installer?
Also, the discussions I saw about windows installers not removing the path on
uninstall is completely false as regards the installers that wix creates, at
least. I've modified the path many tim
