At 11:14 AM 8/12/2002, Cliff Woolley wrote:
The .msi and .exe installers for 2.0.40 are borked... lots of default
stuff (license, etc), and the registry keys created are apparently for
2.0.39 instead of 2.0.40 (or so says one of the several PR's on the
matter).
This was my fault, entirely, so I'm starting with my apologies for leaping
without looking.
I'd upgraded my machine to InstallShield Developer (7.0.4) while the earlier
packages were all built with InstallShield for Windows Installer (1.5.3).
Apparently it's converters were not sufficiently complete.
How soon can these be rebuilt? Should I pull the broken installers in the
meanwhile?
The new binaries are checked into the usual location. I checked the
install against an nmake -f makefile.win INSTDIR=... style install, and
nothing seems to be missing.
Again, my apologies, and I'll take some time to figure out why the ISDE
flavor isn't correct. Since we can no longer obtain ISWI, these need to
be migrated anyways.
And finally, I'll go back to my ancient project of building the perl classes
required to access the .msi and .cab (diamond) interfaces for building
these .msi files programmatically, so we don't run into these problems
again. Really, ISDE (ISWI) were only needed to create the original
dialogs and other packaging. Now that we have a complete package,
it 'should' be pretty trivial to rebuild the .cab file on the fly, and that
would
only require perl and the SDK for someone else to churn out binaries.
Investigating.
Bill
