To do reasonably soon when possible:
------------------------------------

* Install upstream's changelogs (if I can find them in any sort of
  coherent form)

* cernlib script should be tested to make sure it supports upstream versions
  of Cernlib

* If at some point I decide to resurrect hepdb and fatmen binary packages:
  (this will not happen unless I get a specific request by someone who knows
  how they are supposed to be set up)...
  - Write man pages for hepdb and fatmen binaries
  - Set up hepserv, fatsrv with init scripts, etc.

* Split Cernlib into separate source packages with the appropriate
  Build-Depends.  This avoids forcing the buildds to recompile the largely
  unchanging and painful-to-compile Monte Carlo code all the time.
  Unfortunately this will require a lot of work separating patches,
  duplicating build scripts, etc.

* Have separate version numbers (the ones used by upstream) for each major
  Cernlib component.  Will be much easier once source package is split up.

To do after the release of Etch:
--------------------------------

* Split cernlib-base into cernlib-base and cernlib-base-dev packages.
  The former will contain only the current documentation in
  /usr/share/doc/cernlib-base while the latter will contain the cernlib
  script in /usr/bin and the cernlib Autoconf macros from Patrice Dumas.
  All cernlib-related packages will depend on cernlib-base while only
  -dev packages and related tools (kuipc) will depend on cernlib-base-dev.

* Remove backward-compatibility symlinks for pawX11.{dynamic,static},
  and similarly for paw++ and manpages.

To do ONLY if someone employs me at a high salary for these specific purposes:
------------------------------------------------------------------------------

* Fix the whole creaky, out-of-date, Imake-based build system to use GNU
  libtool/automake/autoconf.

* Make COMIS, etc., 64-bit clean so Paw (et al.) work on the architectures
  alpha/amd64/ia64/ppc64/s390x/sparc64 - for bonus points, when dynamically
  linked.  The current state of 64-bit platforms is that Paw only works on
  amd64 (thanks to Harald Vogt), and only when statically linked.