Date: | Tue, 24 Apr 2007 04:51:23 -0400 |
From: | Jeffrey Altman <jaltman@mit.edu> |
To: | kfw-bugs@mit.edu |
Subject: | Build Scripts fail to package with "beta" version |
The build scripts read the version information out of
pismere/athena/include/kerberos.ver but it fails to use the BETA macro
to determine if this is a beta build and if so what beta number it is.
The final file names should be
kfw-<major>-<minor>-<rev>[-beta<beta>]
where [-beta<beta>] is only used if the BETA macro is set in
pismere/athena/include/kerberos.ver
The BETA macro when set must also be used when generating the NSIS
site-local.nsi and WIX site-local.wxi files.
For NSIS, the BETA macro results in "!define RELEASE" not being set and
"!define BETA <beta>" being set where <beta> is the value of the BETA macro.
For WIX, the BETA macro results in <?define Release="1"?> not being set
and <?define Beta="<beta>"?> where <beta> is the value of the BETA macro.
This should be fixed for post KFW 3.2.
pismere/athena/include/kerberos.ver but it fails to use the BETA macro
to determine if this is a beta build and if so what beta number it is.
The final file names should be
kfw-<major>-<minor>-<rev>[-beta<beta>]
where [-beta<beta>] is only used if the BETA macro is set in
pismere/athena/include/kerberos.ver
The BETA macro when set must also be used when generating the NSIS
site-local.nsi and WIX site-local.wxi files.
For NSIS, the BETA macro results in "!define RELEASE" not being set and
"!define BETA <beta>" being set where <beta> is the value of the BETA macro.
For WIX, the BETA macro results in <?define Release="1"?> not being set
and <?define Beta="<beta>"?> where <beta> is the value of the BETA macro.
This should be fixed for post KFW 3.2.