Adam,

I just spent a significant amount of time improving the Xorg 7.4 build
system in the trunk so that I will be able to provide compatible RPMs to
help users migrate from TurboVNC.  Once the final stage of that project
is complete, I will be able to provide binary RPMs and DEBs that we can
release with TigerVNC 1.1 and which will work on RHEL 4 and later.
Eventually, I would like to replace this build system with the new Xorg
7.5 build scripts I developed for Cendio, but those are not yet fully
working, and neither of us has time to debug them.

For the foreseeable future, I will need Xorg 1.5.x support to remain in
the code base.  I am of the school that something should not be removed
unless (a) we are very sure that no one is using it, (b) it is becoming
difficult to maintain, or (c) it is causing verifiable harm.  Xorg 1.5.x
support is doing none of the above.

Darrell

On 4/27/10 8:50 AM, Adam Tkac wrote:
> Hello,
> 
> I would like to remove X.Org 1.5.X support from trunk. In my opinion
> there is no reason to keep it because we have already script which
> builds X, release 7.5, which includes X.Org 1.7.X code.
> 
> Question is if there is a reason to include X.Org 1.6.X support. In my
> opinion it can be removed as well. I think people which compile Xvnc
> themselves can use X.Org 1.7.X and distributors which includes
> X.Org 1.6.X won't rebase their TigerVNC to 1.1.X from 1.0.X. So I
> don't see any benefit from X.Org 1.5.X and 1.6.X support.
> 
> What do you think about it?
> 
> Regards, Adam
> 

------------------------------------------------------------------------------
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Reply via email to