Versioning the CHM Files

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So it looks like you've gone the route of using a fixed URL for the
Compiled Help files that we are bundling with the Windows Installer.

The main problem with that, is that when building the installer, we
basically have to tell it to re-download those files from scratch every
time, because we don't have a way to tell locally if the files are up to
date. And, in fact, it lead to the fact that the 2.0.0-1 installer has
out-of-date help text. (Thanks to DeeJay for finding this.)

IMO, I'd actually rather rebuild the chm files from source as part of
the build process, as that can usually be taught whether things need to
be rebuilt or whether we can just re-use the source. This will become
even more important once we start doing a 2.0.1 release and a 2.1.0b1
release, because at that point, we'll need 2 different CHM files at a
minimum.

Is there a specific reason they cannot be easily rebuilt on demand?

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq9CQAACgkQJdeBCYSNAAOvCgCeIFETMlBrDvHJ8/PCL55AzQ6e
Y5sAoJvKI+nQfYABFlMp9aJfGOJU/idx
=owJZ
-----END PGP SIGNATURE-----