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

[Daniel Stone]

On Mon, Jan 24, 2005 at 08:06:10AM +0100, Roland Mainz wrote:
> Daniel Stone wrote:
> > > Who decides such changes ? AFAIK the Xorg arch board or the Xorg
> > > directory are allowed to make such a drastic change or approve it unless
> > > it goes through a bug.
> > 
> > I don't think this is any more drastic than, say, bringing in a browser plugin.
> 
> The plugin was always there. Since X11R6.3.

Except when it wasn't.

> 1. Daniel: Are you still refusing to undo this commit [YES] / [NO] ?

Yes.

> 2. The plugin was restored upon user request and even added to the
> X11R6.8.x stable branch per request and release-wranglers consens.
> Correct me if I am wrong: You violated that consens...

I have not modified XORG-6_8-branch.  The plugin is still there.  People who
want it can build it, can they not?

> > > BTW: I am the XRX maintainer and I doubt all the non-Debian platforms
> > > are that happy that you disabled xterm in the default build.
> > 
> > xrx != config/cf.
> 
> You did disable it in the default build, right ?

Yes.  Just as you enabled it in the default build.

> > I doubt the Fedora Core people would care much, since they too use the actual
> > upstream source, instead of our lagged copy.
> 
> Other distributions _DO_ care. And for those which don't care is a
> switch provided which should default to |YES|.

If they care, then surely they can expend effort.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.x.org/archives/xorg/attachments/20050124/5bda4ea3/attachment.pgp>