Disable xterm and XRX builds per default / [Fwd: CVS Update: xc (branch: trunk)]

[Keith Packard]

Around 5 o'clock on Jan 25, Daniel Stone wrote:

> I respectfully disagree.  I believe that we should *allow* building of that for
> which we are the upstream source, and do our best (within reasonable limits) to
> ensure that we don't gratuitiously break it, but I think the default install
> should err on the side of sanity.

If there was a separate xrx package that people could download and build, 
I would agree with you -- the 'default' X.org distribution might not want 
to include that piece.  Given that there is not such a package, this makes 
the X.org distribution the canonical source for this software.  Having 
software which is not built by its canonical source seems a bit strange to 
me.

Similarly, we ship and build Composite, Damage and XFixes by default, but 
we don't expect huge numbers of people to ever use them (at least not in 
their current state).

If the default installation of xrx exposes the machine to significant 
potential problems (as Composite does by regularly crashing X servers), 
then we should fix that.

> AIUI, building DRI from Mesa can basically be done today.

Ajax says "almost".  I can't wait.

-keith


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20050124/d113ad1a/attachment.pgp>