names reason (lack of tcl/tk in tree). BEsides that, XF86Setup - as the 
   name says - is rather i386 specific, and to make it useful on about all 
   NetBSD platforms, quite some work would be necessary.


most netbsd platforms do *not* require this functionality.  but i'm
not sure about your observation:  `XFree86' has `86' in the name also
but it supports many of our platforms.  the name XF86Setup to me is
derived form the whole package name, not because it's x86 specific.
(xfree86 _used to_ be x86 specific, which is where it's name came
from).  does XF86Setup work on the shark? or the alpha?  i imagine
that they would need it.  when the sparc64 port does the pci machines,
perhaps it will also...


having recently discovered how much of a *pain in the ass* configuring
xf86 is, i *strongly* agree with chris' position on this.  we should be
shipping XF86Setup.  i don't care how it's built and packaged -- the
nicer the better, but it *should* be there.


.mrg.