Some hints for maintainers

(Note: calling configure with --enable-maintainer-mode should enable
all maintainer options, but this seems broken somehow (e.g. `make
depend' in texk/xdvik/ doesn't work). So I usually remove the `@MAINT@'
comments manually, as described below.)

- After changing a configure.in run 'sh reautoconf' in the top directory

- After adding a check to configure.in, sometimes acconfig.h needs to
  be adapted too (see e.g. USE_XAW_PANNER, HAVE_LIB_XP). After doing that,
  run:

  /usr/bin/autoheader -m ../etc/autoconf
  /usr/bin/autoconf -m ../etc/autoconf

  (requires autoconf-2.13 in the path, which is /usr/bin in my case.)

- to add a new check to configure, e.g. for xdvik, add the macro name to
  texk/xdvik/configure.in (add the macro definition to texk/xdvik/aclocal.m4
  if needed), and run either
  autoconf --macrodir=../etc/autoconf configure.in > configure
  or remove the `@MAINT@' comments from texk/make/config.mk and call
  make configure

- to re-make the dependencies, remove the @MAINT@ prefixes from
  texk/make/rdepend.mk,
  and call
  make depend
  from the texk/xdvik/ directory.

  (NOTE: this needs to be done after the call to `configure' so that
  all temporary headers and Makefiles are in place!)

---

To update libraries and build files from TeX Live:

In the main directory, the following files belong to xdvik:

	BUGS
	CHANGES
	INSTALL
	README.CVS
	README.xdvik
	README_maintainer
	TODO
	config/		(empty directory)

All others should be updated from TL (or deleted if no longer present there):

---

When updating t1lib from upstream:

0. cd libs
1. find t1lib -name CVS -type d -prune -o -type f -print | xargs rm -fv
2. Unpack new t1lib into old directory
3. Apply t1lib.diff to enable KPATHSEA_DEBUG of fopen/fclose tracing.
   And perhaps also psenc.diff if RMZ has not incoroprated a ps compatible
   encoding vector parser.
4. cvs -n update
   For all U files do: cvs remove
   For all ? files do: cvs add
   For all M files do: nothing
5. cvs commit in your own time

---

- enable a reasonable level of compiler warnings with:
  ./configure --enable-compiler-warnings
