[COMMIT] Eliminate some non-X11 build failures

[Stephen J. Turnbull]

On 10/16/07, Mike Kupfer <mike.kupfer at sun.com> wrote:
> >>>>> "Aidan" == Aidan Kehoe <kehoea at parhasard.net> writes:
>
> Aidan> But, Mike, as I said, no-one's holding themselves to that right
> Aidan> now, and while an occasional check on a non-X11 build would be
> Aidan> nice, don't feel yourself obliged to do it.
>
> Okay, thanks.
>
> I do think there's value in discussing how the package tree should be
> structured and built, and what the requirements will be for package
> maintainers.  As you pointed out, there's Windows now, and Carbon is
> coming.  And eventually 21.5 will be the stable branch.  What should the
> package tree look like then?  For example, will we still have a separate
> mule package cluster?

Eventually we want to invert the subtree structure from content-type/package
to package/content-type (among other things, this will allow true run-in-place
in a package tree, and will make Emacspeak and the Java support much
happier since they reference help and other files relative to package root.

The Mule package cluster will continue to exist as long as non-unibyte
characters crash the non-Mule build of the "retired" tree.  Since 21.4 is
vulnerable, that's "for the foreseeable future".

I think it's possible to reduce the burden on package maintainers, but
how much I'm not sure.