From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22727 invoked by alias); 28 Jul 2008 17:17:38 -0000 Received: (qmail 22709 invoked by uid 22791); 28 Jul 2008 17:17:36 -0000 X-Spam-Check-By: sourceware.org Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.180) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 28 Jul 2008 17:17:08 +0000 Received: by py-out-1112.google.com with SMTP id w53so2401788pyg.25 for ; Mon, 28 Jul 2008 10:17:06 -0700 (PDT) Received: by 10.64.180.15 with SMTP id c15mr10074275qbf.89.1217265425139; Mon, 28 Jul 2008 10:17:05 -0700 (PDT) Received: from ?192.168.0.101? ( [24.76.249.6]) by mx.google.com with ESMTPS id k29sm22346775qba.7.2008.07.28.10.17.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 28 Jul 2008 10:17:04 -0700 (PDT) Message-ID: <488DFF11.8030904@users.sourceforge.net> Date: Mon, 28 Jul 2008 17:17:00 -0000 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: cygwin-apps@cygwin.com Subject: [RFC] 1.7 Packaging: X11 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-07/txt/msg00153.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Our X11R6 hasn't been updated in almost three years now. Since then, X.org has moved to a modular R7 where each library, executable, font set, etc. have their own autotooled package. It seems that our X11 is used for two different things: 1) to build and run X11(/GTK+/GNOME/Qt/KDE) GUI programs for Cygwin, or 2) to remote desktop from other *NIX boxes. I have been using the client side of X11R7 for a couple years now, and it works beautifully. I've been able to build and run almost all of both GNOME and KDE with very few issues. The one problem I have had is getting the server to build and/or work, as I've mentioned on several occasions, so in the meantime I've been using Xming. Since I wasn't comfortable with an incomplete X11 upgrade, I never got this into the distro as I had intended, and this is where Ports and the distro diverged, as I was unable to update anything X11-dependent without an update to X11 itself. With 1.7 coming, I think now is the time to rethink this. The monolithic tree is now obsolete, and I can't even imagine trying to maintain it. OTOH the modular packages are essentially like any other, and are very easy for someone (or even several people) to maintain. I am very comfortable with the client side, and I am prepared to update the headers, libraries, and apps for 1.7 and maintain it within the distro. Furthermore, I am willing to coordinate an effort to get XWin ported and working, providing there are those that would commit to help. Until XWin R7 is working, either people will need to use Xming, or the old R6 XWin. It's not perfect, but some would say that it fits with WJM. :-) OTOH, I've never used X11 as a remote desktop, since I've never had such a setup, so I'm really not able to help much with the many questions on that topic. So what I think we need is a co-maintainership. I can handle the packaging and client-side issues, and other(s) can help port XWin and handle server-side issues. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiN/xEACgkQpiWmPGlmQSPOjACffkpcRxSWd8i8MvGPOD0mLmVd vCsAn0rE+sGpJWxZSaMUoPLjBlqvJLz8 =v2n8 -----END PGP SIGNATURE-----