There have been a number of bugs in the last year caused by people
updating the j2sdk build image, but failing to either make the necessary
modifications to the SVr4 packages, or to ask the installer group to do it.
This is likely to continue happening: people just aren't aware of the
SVr4 packages. Education would no doubt help, but wouldn't solve the
problem completely.

So here's an item to place on a wish list for some future release. Rewrite
the package makefiles (make/pkgdefs) so that every file or symlink in the j2sdk
image automatically winds up in exactly one SVr4 package. Use heuristics
to determine what goes where, rather than an explicit enumeration of files
(such lists always get stale). Have a single "special case" list in
one place (not scattered among several makefiles) that handles all the
exceptions, exclusions, and other oddities.

The heuristics I have in mind would be something like:

- If a file contains "sparcv9" in its name then it goes into one of the 64-bit
  packages, otherwise it does not.
- If a file contains "_g" in its name then it goes in one of the debug
  packages, otherwise it does not (but watch out for
  jre/lib/zi/Atlantic/South_Georgia!)
- If a file name begins with "jre/" then it goes in one of the runtime
  packages (j3rt or j3rtx).
- A file named bin/foo goes in j3dev, unless there is also a jre/bin/foo, in
  which case both go in j3rt. Similarly for bin/sparcv9/foo.

And so on.