Re: Looking for Cygwin/X maintainer
Christopher Faylor wrote: Our Cygwin/X maintainer seems to have disappeared so it looks like we, once again, are looking for volunteers to be the go to person for Cygwin/X. That would mean building new releases, handling problems in this mailing list, and keeping the cygwin-xfree web site up-to-date. I've been working on packaging modular X11 for the last few weeks. I've finished everything relevant in util, proto, lib, data, and most of app; all that's left now is the rest of app, fonts, docs, and xserver. I don't want to commit to this yet, until I manage to get everything packaged and running, but you should know that it's being worked on. You can check my progress at: ftp://sunsite.dk/projects/cygwinports/release/X11/ Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
On Sat, Apr 15, 2006 at 10:54:16PM -0500, Yaakov S (Cygwin Ports) wrote: Christopher Faylor wrote: Our Cygwin/X maintainer seems to have disappeared so it looks like we, once again, are looking for volunteers to be the go to person for Cygwin/X. That would mean building new releases, handling problems in this mailing list, and keeping the cygwin-xfree web site up-to-date. I've been working on packaging modular X11 for the last few weeks. I've finished everything relevant in util, proto, lib, data, and most of app; all that's left now is the rest of app, fonts, docs, and xserver. I don't want to commit to this yet, until I manage to get everything packaged and running, but you should know that it's being worked on. You can check my progress at: ftp://sunsite.dk/projects/cygwinports/release/X11/ Thanks for the update. I look forward to the day when this void will be filled. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
Charles Wilson wrote: Alan originally planned to migrate any specific changes in the CYGWIN branch over to HEAD: http://cygwin.com/ml/cygwin-xfree/2005-10/msg00122.html I'll be working on getting whatever changes exist on [the CYGWIN] branchover into the mainline trunk code next. But that statement was made AFTER the 6.8.99.901 test release and there is no indication of whether that actually happened -- or if it was even necessary (it's possible that there were no differences between the CYGWIN branch and the HEAD branch as of 27-Oct-2005). Nor is it known whether any of these CYGWIN-branch-only changes, IF they even exist, were merged to the modular codebase. FWIW, a grep for CYGWIN in the libraries turns up very few source files, but hw/xwin is present in the server source. X.org's 7.0 release contained EXACTLY the same code as their 6.9 release, only in modularized form using autotools instead of imake. However, even tho Alan was able to build a release-candidate for the monolitic 6.9 code on cygwin, it is unknown whether that same code, over in the modularized tree, can be built on cygwin. Are cygwin's autoconf/automake/libtool up to the task? Did the folks who put together the configure.ac and Makefile.am files make any assumptions that are not true for cygwin? Unknown. The following packages need to have '-no-undefined' added to the *_la_LDFLAGS: libXdmcp liblbxutil libXmu libXaw libXevie libXfont libXi libXres. Other issues I've found so far: * libX11: if X_LOCALE is not defined in general, then at least XSetLocale needs to be forced into the library for compatibility with 6.8. * liblbxutil: there's an $(EXEEXT) missing in a custom make rule, and there's an unaccounted dependency on libXdmcp. * libXaw: the install-exec-hook is Linux-specific. Alan's original plan was To switch to the modular build without a doubt. and not remain on the monolithic (and now frozen/dead/buried) codebase, so the keep a big patch method being used by Colin for xming is not applicable. However, it is unknown how much progress Alan and others were able to make in switching to the modular build -- never mind adapting the monolithic-oriented release and pakaging scripts. It is unknown how much of Colin's stuff is helpful for cygwin or already ported/merged-into to the modular codebase. The release and packaging scripts -- which do not appear to be publicly available anyway -- need to be modified to work with the modular architecture. It is unknown what the status of that effort is. With the modular system, you can use the g-b-s as well, one for each tarball. See the following for more details: http://xorg.freedesktop.org/wiki/ModularDevelopersGuide X11R7.0 and beyond, according to the xorg folks, is supposed to live in /usr and NOT /usr/X11R6 (and not /usr/X11R7, either). It is unknown what effect this will have on other cygwin packages. generic-build-script based builders will need to change --x-libraries= statements, but beyond that? Runtime effects should be minimal, although folks will need to remove their cygwin-x shortcuts and re-run (a new, updated) X-start-menu-icons.sh. For one, all other packages should be moved ASAP to /usr, and this can precede X11R7.0. The affected packages outside of xorg-x11 itself are: freeglut fvwm ghostscript-x11 gv lesstif nedit openbox tcm tetex-x11 transfig WindowMaker Xaw3d XmHTML xfig xfig-lib xgraph xmon The update to libXft needs to include a postinstall script along the lines of: find /usr/lib -name '*.la' | xargs -r sed -i -e 's:/usr/X11R6/lib/libXft\.la:/usr/lib/libXft\.la:' A similar solution is needed for any other libtool libraries being moved. Also, much of the documentation in the Contributor's Guide would need to change, to reflect new build procedures -- both for how to make setup.exe-style packages from a modular xorg tree and I just want to build and test and have no interest in making release packages. Does anybody even have a clue as to how these instructions would need to change? Has *anybody* tried to build the modular codebase? I've got as far as the necessary utils, and all protos and libs; I haven't got to the server yet. So far it's pretty straight forward, just very tedious. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
Alan Hourihane wrote: But, yet more thoughts. Given that Chris Corinna want a more active person to maintain Cygwin/X - I should stand down anyway. Thanks for having me. Please don't go away mad. :-) Better, please don't go away, even if you do stand down. Even beyond the be really active on the mailing list thing, tho, the current status of cygwin/x needs a bit of explanation if ANYbody is going to take over the maintainership. I'd be a bad choice -- heck, I'm doing a pretty poor job with the packages I supposedly DO maintain -- so I'm not volunteering -- but I can see some issues even so. Before Alan steps down, or during his transition period, there are a few questions that need answering before the next sucker^Wvolunteer could even begin to get a handle on things. What is the current status of cygwin/X source code, release methodology, and what are the plans for the future and the status of their implementation? I'll tick off what I think is true, and look forward to being corrected. 6.8.2.0-x (where x=1,2,3,4 depending on the specific package) The current stable cygwin-xorg release is 6.8.2.0, which is a monolithic imake-driven build and lives in /usr/X11R6. It can be built by either downloading all the relevant -src packages, unpacking them in the same location, OR doing a cvs checkout from the CYGWIN branch cvs -d :pserver:[EMAIL PROTECTED]:/cvs/xorg co -r CYGWIN-6_8_2-MERGE xc I'm ignoring cygwin-x-docs for right now. Because this is a monolithic release, the instructions here or here http://x.cygwin.com/docs/cg/prog-build-native.html http://x.cygwin.com/docs/cg/prog-build-cross.html will work. This release was originally packaged by Alexander Gottwald in July 2005. It is a mystery how this packaging was accomplished, as http://x.cygwin.com/docs/cg/prog-distribution.html was never updated (it currently reads Wait for these instructions to be updated, sometime after 2004-04-03.) ago is still around, monitors the list, and maintains a few (non-core) X-related packages like X-startup-scripts, X-start-menu-icons, and run. However, he is unavailable for advice or assistance with the core cygwin/x stuff: http://cygwin.com/ml/cygwin-xfree/2005-07/msg00118.html 6.8.99.901-1 -- The cygwin-xorg test release is 6.8.99.901-1 which is a monolithic imake-driven build, based off of one of the final release candidates for xorg-6.9.0 (aka X11R6.9). It also lives in /usr/X11R6. It can be built by either downloading all the -src packages, unpacking them in the same location, or doing a cvs checkout from the main branch cvs -d :pserver:[EMAIL PROTECTED]:/cvs/xorg co -r XORG-6_8_99_901 xc Again, ignoring cygwin-x-docs. Also again, because this is a monolithic release, these instructions http://x.cygwin.com/docs/cg/prog-build-native.html http://x.cygwin.com/docs/cg/prog-build-cross.html will work. This release was originally packaged by Alan Hourihane in October 2005. Obviously there were changes to the source code between 27 Oct 2005 (when Alan packaged our 6.8.99.901 version) and 21 Dec 2005 (when the real xorg 6.9.0 was released, and the xc monolithic tree was frozen). It is unknown if any of those changes materially affect cygwin/X. Again, the packaging is a mystery, because while Alan stated in http://cygwin.com/ml/cygwin-xfree/2005-10/msg00100.html that currently the scripts that build and package Cygwin/X are based on the monolithic tree I, at least, can't find those scripts in the cvs repository. BUGS: - Nicholas Wourms reported in http://cygwin.com/ml/cygwin-xfree/2005-10/msg00127.html that 'xcursorgen and the icon sets' were missing from this test package. (He also mentioned the DPS libraries, but that's not a bug: they are being phased out by xorg team). This release is still in 'test' after four months. Plans and status thereof (1) CYGWIN branch merge-to-HEAD Alan originally planned to migrate any specific changes in the CYGWIN branch over to HEAD: http://cygwin.com/ml/cygwin-xfree/2005-10/msg00122.html I'll be working on getting whatever changes exist on [the CYGWIN] branchover into the mainline trunk code next. But that statement was made AFTER the 6.8.99.901 test release and there is no indication of whether that actually happened -- or if it was even necessary (it's possible that there were no differences between the CYGWIN branch and the HEAD branch as of 27-Oct-2005). Nor is it known whether any of these CYGWIN-branch-only changes, IF they even exist, were merged to the modular codebase. (2) Migration to modular tree Because xorg is transitioning to a modularized build architecture using the autotools instead of imake, X11R6.9 is the last monolithic release -- and the xc directory is now CLOSED for any further development as of 21 Dec 2005 (http://lists.freedesktop.org/archives/xorg/2005-December/011752.html). Thus, any
Looking for Cygwin/X maintainer
Our Cygwin/X maintainer seems to have disappeared so it looks like we, once again, are looking for volunteers to be the go to person for Cygwin/X. That would mean building new releases, handling problems in this mailing list, and keeping the cygwin-xfree web site up-to-date. If you are interested please reply to this message. Lets keep it on the list please. cgf/corinna -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
On Thu, 2006-03-02 at 10:45 -0500, Christopher Faylor wrote: Our Cygwin/X maintainer seems to have disappeared so it looks like we, once again, are looking for volunteers to be the go to person for Cygwin/X. That would mean building new releases, handling problems in this mailing list, and keeping the cygwin-xfree web site up-to-date. If you are interested please reply to this message. I'm still here, but v. busy. So if someone does want to take over - feel free. Alan. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
On Mar 2 15:49, Alan Hourihane wrote: On Thu, 2006-03-02 at 10:45 -0500, Christopher Faylor wrote: Our Cygwin/X maintainer seems to have disappeared so it looks like we, once again, are looking for volunteers to be the go to person for Cygwin/X. That would mean building new releases, handling problems in this mailing list, and keeping the cygwin-xfree web site up-to-date. If you are interested please reply to this message. I'm still here, but v. busy. So if someone does want to take over - feel free. It would really be helpful for the Cygwin/X project if somebody could take over. We would really appreciate if somebody with more time to reply to problems on this list and to look for bug-fixes etc. would volunteer. Thanks in advance, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
On Thu, Mar 02, 2006 at 05:00:48PM +0100, Corinna Vinschen wrote: On Mar 2 15:49, Alan Hourihane wrote: On Thu, 2006-03-02 at 10:45 -0500, Christopher Faylor wrote: Our Cygwin/X maintainer seems to have disappeared so it looks like we, once again, are looking for volunteers to be the go to person for Cygwin/X. That would mean building new releases, handling problems in this mailing list, and keeping the cygwin-xfree web site up-to-date. If you are interested please reply to this message. I'm still here, but v. busy. So if someone does want to take over - feel free. It would really be helpful for the Cygwin/X project if somebody could take over. We would really appreciate if somebody with more time to reply to problems on this list and to look for bug-fixes etc. would volunteer. And to clarify - both Corinna and I sent Alan personal email asking for feedback before I sent out my note. I wasn't trying to surprise Alan by sending that note. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
On Thu, 2006-03-02 at 12:09 -0500, Christopher Faylor wrote: On Thu, Mar 02, 2006 at 05:00:48PM +0100, Corinna Vinschen wrote: On Mar 2 15:49, Alan Hourihane wrote: On Thu, 2006-03-02 at 10:45 -0500, Christopher Faylor wrote: Our Cygwin/X maintainer seems to have disappeared so it looks like we, once again, are looking for volunteers to be the go to person for Cygwin/X. That would mean building new releases, handling problems in this mailing list, and keeping the cygwin-xfree web site up-to-date. If you are interested please reply to this message. I'm still here, but v. busy. So if someone does want to take over - feel free. It would really be helpful for the Cygwin/X project if somebody could take over. We would really appreciate if somebody with more time to reply to problems on this list and to look for bug-fixes etc. would volunteer. And to clarify - both Corinna and I sent Alan personal email asking for feedback before I sent out my note. I wasn't trying to surprise Alan by sending that note. That's interesting - because I didn't get anything from either of you. Alan. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
On Thu, 2006-03-02 at 12:09 -0500, Christopher Faylor wrote: On Thu, Mar 02, 2006 at 05:00:48PM +0100, Corinna Vinschen wrote: On Mar 2 15:49, Alan Hourihane wrote: On Thu, 2006-03-02 at 10:45 -0500, Christopher Faylor wrote: Our Cygwin/X maintainer seems to have disappeared so it looks like we, once again, are looking for volunteers to be the go to person for Cygwin/X. That would mean building new releases, handling problems in this mailing list, and keeping the cygwin-xfree web site up-to-date. If you are interested please reply to this message. I'm still here, but v. busy. So if someone does want to take over - feel free. It would really be helpful for the Cygwin/X project if somebody could take over. We would really appreciate if somebody with more time to reply to problems on this list and to look for bug-fixes etc. would volunteer. And to clarify - both Corinna and I sent Alan personal email asking for feedback before I sent out my note. I wasn't trying to surprise Alan by sending that note. But, yet more thoughts. Given that Chris Corinna want a more active person to maintain Cygwin/X - I should stand down anyway. Thanks for having me. Alan. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
On Mar 2 17:28, Alan Hourihane wrote: On Thu, 2006-03-02 at 12:09 -0500, Christopher Faylor wrote: On Thu, Mar 02, 2006 at 05:00:48PM +0100, Corinna Vinschen wrote: On Mar 2 15:49, Alan Hourihane wrote: On Thu, 2006-03-02 at 10:45 -0500, Christopher Faylor wrote: Our Cygwin/X maintainer seems to have disappeared so it looks like we, once again, are looking for volunteers to be the go to person for Cygwin/X. That would mean building new releases, handling problems in this mailing list, and keeping the cygwin-xfree web site up-to-date. If you are interested please reply to this message. I'm still here, but v. busy. So if someone does want to take over - feel free. It would really be helpful for the Cygwin/X project if somebody could take over. We would really appreciate if somebody with more time to reply to problems on this list and to look for bug-fixes etc. would volunteer. And to clarify - both Corinna and I sent Alan personal email asking for feedback before I sent out my note. I wasn't trying to surprise Alan by sending that note. That's interesting - because I didn't get anything from either of you. Chris sent a mail on 2 Feb 2006, I'm cc'ed. I sent a follow-up mail on 20 Feb 2006, Chris was cc'ed. Both mails were sent to Alan Hourihane alanh AT fairlite DOT demon DOT co DOT uk Text: Hi Alan, Are you still interested in being the cygwin/x maintainer? I haven't seen much activity from you in the mailing list. I understand completely if you don't have the time for this but I think we need really need some active involvement on the mailing list and we probably need a new release as well. Should we open up this up for other volunteers? cgf My follow-up mail was just a ping. It's strange that both messages should be lost or being munched by a spam filter. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
