Thanks to quick work from Rob Murawski, OpenAFS for Windows now supports
both NSIS 2.0b3 and 2.0b4. The NSIS version is automatically detected
at build time.

Jeffrey Altman


Murawski, Rob wrote:

Yes, it seems that when the MUI was upgraded, they changed a number of
the macros and constants.  Basically, the answer on the NSIS FAQ is that
scripts for 2.0b3 are not compatible with 2.0b4.

The NSIS CVS now has a version number constant in it and I am working on
updating the build process to determine which version of NSIS is being
used (for 2.0b3 and 2.0b4).  There are some nice new features in 2.0b4
I'd like to use, but, in a way, I'd like to see a non-beta version of
NSIS for us to use in a production code release.  When we get closer to
a release, we'll need to lock in on a particular version of NSIS.

Also, my hope is that the Korean MUI support is in 2.0b4 and we can
re-enable that code in the installer.


-Rob


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



Reply via email to