…the config.mk file
Now, if you know that the path to the chezweave or cheztangle scripts written for the petite target will also contain the chezweb.ss file, then it is not necessary to define CHEZWEBHOME. This allows for in place builds. When doing a general install it is still necessary to make sure that CHEZWEBHOME is set for petite builds.
This fixes an issue where we strip off too much whitespace from the files. This adds back one newline between each of the concatenated chunks when tangling to help with things. This only affects tangling, and it does not guarantee whitespace preservation, only that each line will continue to be a line on its own.
Somehow this bug slipped through, but if you tangle an unstarred section that has no text body, version 2.0 will die on you. This fixes that bug. I have also added some more documentation and cleaned up a bit of things, including throwing in some index entries where I needed them.
This change makes changes to the scripts and to the way that we load code to enable people who only have petite to use the system. Namely, it recognizes the CHEZWEBHOME environment variable so that an user can point to the runtime.ss and chezweb.ss files that would normally be compiled into the system, but which are now also distributed as part of the LIBDIR contents. I don't particularly like this solution as it greatly increases the number of files that need to be installed, but it does have the advantage of working with Petite. Notably, this does not change what is required for the compiled version. You still only need the two compiled scripts and the TeX file to actually use ChezWEB if it is compiled.