SCO port update - what now?
kean at armory.com
Fri Jun 10 09:09:18 PDT 2005
> Looking through the patch, it seems to be pretty reasonable, mostly
> SCO-specific, and nothing jumps out at me from the rest. (I'm not
> sure the changes to whether monitor refresh rates are commented out
> or not in the generated config file should be #ifdef SCO but rather
> some more general #ifdef, but that can be cleaned up later.) I don't
Right. Jay Cotton and I have tentative plans to overhaul xorgcfg and
bring it into the modern age. I was delayed in working with him on
that by day job pressures, but thats mostly a thing of the past now.
For what its worth, if Xorg folks like keeping track of where this
stuff is deployed, SCO OpenServer 6, due to be released on June 22,
uses Xorg 6.8.2 as its one and only X server. We've dropped the old
SGI NFB-based "Xsco" server.
> see a reason why you shouldn't merge it to head once you have the
> changelog done if you think it's ready to go.
I'm working on the ChangeLog entry today. Its fairly substantial.
But once it is done, *how* do I merge to head? I thought the head
was read-only to mere mortals?
> I would suggest you contact Thomas Dickey about incorporating the
> xterm changes into the xterm sources he maintains, because we're
> trying not to fork from his source if possible.
Good call. I will isolate the xterm patches and do that.
More information about the xorg