On 12/27/2011 01:40 PM, DRC wrote: > Let's be clear here. Composite is disabled *only* in the legacy-friendly > build, Hah, thanks for the (important) clarification!
> because the window managers on some legacy systems don't work properly with > Composite enabled. The legacy-friendly build is a lowest common denominator > build. It is intended to provide the broadest compatibility, not the broadest > feature support. TigerVNC really relies upon distro maintainers or distro > enthusiasts to fully support newer platforms (Fedora, for instance, or even > RHEL 6.) My customers are still on RHEL 5, so that's the platform that will > get the most attention from me. I'm volunteering the labor to provide project > builds, so If you want my builds to have better support for non-legacy > platforms, your best bet is to submit a patch. I'll be glad to test it, but I > don't have time to develop it myself. Updating the debian packages to build properly against the host headers has been on my TODO list for months now, I'll try to get around to it. I was hoping that (debian) distributions would have picked it up themselves by now. Antoine > > On Dec 26, 2011, at 2:12 AM, Antoine Martin <anto...@nagafix.co.uk> wrote: > >> On 12/26/2011 02:07 PM, DRC wrote: >>> Please read the bug report on this (I would link to it, but I'm not in >>> front of a real computer.) It explains in more detail why it was necessary >>> to remove the extension by default. It may be possible to enable it at >>> run-time. I don't know. Composite isn't a priority for my project, so I'm >>> not incented to look into it further, but I'd be happy to evaluate a patch >>> if you or someone else wants to submit it. >> I agree with Sebastian, this looks like a serious regression to me. >> There are many applications & desktop environment that rely on the >> composite extension nowadays.. >> I don't understand why removing compatibility with something that is on >> the rise can be seen as the right way forward, aren't we trying to >> attract more people not less? >> >> Cheers >> Antoine >> >> >>> >>> On Dec 26, 2011, at 12:59 AM, sebastian nielsen >>> <nielsen.sebast...@gmail.com> wrote: >>> >>>> Why was the composite extension completely removed from the TigerVNC >>>> package? I found a post in the list SVN annouce archive that said it >>>> was incompatible with some legacy systems and provided bad results, >>>> and in new systems its not required at all. >>>> ( http://permalink.gmane.org/gmane.network.vnc.tigervnc.scm/1054 ) >>>> >>>> My suggestion is that Composite extension is readded to the TigerVNC >>>> package, but default disabled, and has to be enabled with +composite. >>>> (2 new commandline options could be added: +/-composite : Enables or >>>> disables composte extension, like +/- render), then it wont cause any >>>> problems with legacy RHEL < 5 systems. >>>> >>>> I currently use VNC to serve a application terminal server via xinetd >>>> via Xvnc -inetd, and its numerous applications that REQUIRE >>>> "composite" to be present and refuse to launch at all if Composite is >>>> not present. >>>> Even if its works bad, does bad rendering and is incompatible with >>>> some systems, at least make it available for enabling/disabling at the >>>> command line "at your own risk". >>>> I really dont care if Composite renders things awfully bad, the >>>> important thing here is that my applications at least launch. >>>> >>>> When trying to enable the composite extension with +extension >>>> Composite, it just tells me: >>>> >>>> "Extension "Composite" is not recognized >>>> Only the following extensions can be run-time enabled:" >>>> >>>> and then a list of extensions where Composite is not present. >>>> >>>> >>>> The "fix" was to download a version that was uploaded prior to 1 >>>> october 2011, that had Composite support compiled in, but should I >>>> really need to use a old version to get composite support? >>>> >>>> It RHEL < 5 complains where Composite is disabled but present, why not >>>> upload 2 versions to SF.net then, one "with-composite" and one >>>> "wo-composite". >>>> >>>> >>>> Best regards, Sebastian Nielsen >>>> >>>> ------------------------------------------------------------------------------ >>>> Write once. Port to many. >>>> Get the SDK and tools to simplify cross-platform app development. Create >>>> new or port existing apps to sell to consumers worldwide. Explore the >>>> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join >>>> http://p.sf.net/sfu/intel-appdev >>>> _______________________________________________ >>>> Tigervnc-users mailing list >>>> Tigervnc-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/tigervnc-users >>> >>> ------------------------------------------------------------------------------ >>> Write once. Port to many. >>> Get the SDK and tools to simplify cross-platform app development. Create >>> new or port existing apps to sell to consumers worldwide. Explore the >>> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join >>> http://p.sf.net/sfu/intel-appdev >>> _______________________________________________ >>> Tigervnc-users mailing list >>> Tigervnc-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/tigervnc-users >> >> >> ------------------------------------------------------------------------------ >> Write once. Port to many. >> Get the SDK and tools to simplify cross-platform app development. Create >> new or port existing apps to sell to consumers worldwide. Explore the >> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join >> http://p.sf.net/sfu/intel-appdev >> _______________________________________________ >> Tigervnc-users mailing list >> Tigervnc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/tigervnc-users ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Tigervnc-users mailing list Tigervnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-users
