September 2005 - Cvs-hugs

cvs commit: hugs98/libraries configure.ac
by Ross Paterson 23 Sep '05

23 Sep '05

ross 2005/09/23 16:27:23 PDT Modified files: libraries configure.ac Log: cosmetic rearrangement Revision Changes Path 1.13 +3 -7 hugs98/libraries/configure.ac

1 0

cvs commit: hugs98 configure.ac
by Ross Paterson 23 Sep '05

23 Sep '05

ross 2005/09/23 16:26:57 PDT Modified files: . configure.ac Log: modernize host setting Revision Changes Path 1.41 +16 -23 hugs98/configure.ac

1 0

cvs commit: hugs98/docs/users_guide Makefile.in htmlhelp.xsl
by Ross Paterson 21 Sep '05

21 Sep '05

ross 2005/09/21 11:34:42 PDT Modified files: docs/users_guide Makefile.in Added files: docs/users_guide htmlhelp.xsl Log: generation of HTMLhelp. Assumes xsltproc & hhc without checking. Revision Changes Path 1.17 +20 -6 hugs98/docs/users_guide/Makefile.in

1 0

cvs commit: hugs98/libraries/tools convert_libraries
by Ross Paterson 21 Sep '05

21 Sep '05

ross 2005/09/21 04:16:20 PDT Modified files: libraries/tools convert_libraries Log: move haskell-src, network and unix packages from core to extras. Revision Changes Path 1.26 +7 -13 hugs98/libraries/tools/convert_libraries

1 0

Windows installer
by Neil Mitchell 20 Sep '05

20 Sep '05

Hi, I'm not particularly overjoyed with an approach which means the tools to build a release installer are not available in the CVS, as this kind of goes against open source (and more practically, it means I personally can't build test releases). I propose that either: 1) The tools used to make the current installer .msi files make themselves known to the world, along with appropriate documentation and scripts. 2) I (or someone else) writes an MSI file generator, probably using the free Wix toolset. 3) I (or someone else) writes an NSIS installer, which is an .exe installer based on the NSIS toolkit, Google seems to now use this as their preferred installer setup, so it can't be too bad. 4) I (or someone else) writes an installer from the ground up. Its not that much work, as I already have about 98% of the code from writing an installer from the Pingus project. The installer is a simple cat installer.exe data.zip > winhugs.exe installer, so it allows making an easy distribution from a zip file, even under Linux. Obviously 1 would be least work if feasible. If I was going to write an installer for the Windows build, which one would people prefer out of 2, 3 and 4? Does anyone use the large scale deployment options found in a .msi, and are those options even in the WinHugs .msi file? Thanks Neil

2 2

cvs commit: hugs98 hugs98.nsi
by Ross Paterson 20 Sep '05

20 Sep '05

ross 2005/09/20 16:23:08 PDT Added files: . hugs98.nsi Log: An attempt at an NSIS (http://nsis.sourceforge.net/) installer script for Hugs -- fails on unpacking for me, though.

1 0

cvs commit: hugs98/docs/users_guide hugs-ug.xsl
by Ross Paterson 19 Sep '05

19 Sep '05

ross 2005/09/19 16:27:25 PDT Modified files: docs/users_guide hugs-ug.xsl Log: tweak treatment of ToCs. Revision Changes Path 1.2 +10 -3 hugs98/docs/users_guide/hugs-ug.xsl

1 0

cvs commit: hugs98/libraries aclocal.m4 configure.ac
by Ross Paterson 19 Sep '05

19 Sep '05

ross 2005/09/19 16:26:24 PDT Modified files: libraries aclocal.m4 configure.ac Log: drop `inline extern' test -- it belongs in the individual libraries. Revision Changes Path 1.5 +0 -45 hugs98/libraries/aclocal.m4 1.12 +0 -1 hugs98/libraries/configure.ac

1 0

cvs commit: hugs98/libraries aclocal.m4
by Ross Paterson 19 Sep '05

19 Sep '05

ross 2005/09/19 16:02:33 PDT Modified files: libraries aclocal.m4 Log: delete unused macro Revision Changes Path 1.4 +0 -104 hugs98/libraries/aclocal.m4

1 0

cvs commit: hugs98 aclocal.m4
by Ross Paterson 19 Sep '05

19 Sep '05

ross 2005/09/19 16:02:07 PDT Modified files: . aclocal.m4 Log: extra quoting Revision Changes Path 1.15 +5 -5 hugs98/aclocal.m4

1 0