On 10/29/08, Edward O'Callaghan <victoredwardocallaghan at gmail.com> wrote: > Right.. > Not sure what you mean about xcb being large and complex ? > So what am I to do to accelerate this process ?
Edward, Alan is right. Complexity begins when you have to maintain an entire puzzle of pieces - all together, all at once, everywhere. Not when somebody hits a default ./configure && make locally at home (w/o having to care for or to fear interdependencies). Simple example: lib/libxcb in version you proposed (the first subdir I created) is so friendly to depend on Python 2.5, but on my snv_95 box the version of /usr/sfw/bin/python is only 2.4.4, so what now? Either decrease xcb version, or try if it is actually compatible to 2.4.4, or wait until Solaris comes with 2.5, or build an own temporary semi-official python package (no!, not fox's biz), or depend on some external repo ... etc. checking for a thread-safe mkdir -p... /opt/sfw/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether /usr/sfw/bin/python version >= 2.5... configure: error: too old *** Error code 1 make: Fatal error: Command failed for target `build_32/libxcb-1.1.91/Makefile' Current working directory /media/0A/fox-gate/fox-gate__hg20081025sat/fox-gate/fox-gate/XW_NV/open-src/lib/libxcb *** Error code 1 make: Fatal error: Command failed for target `build_32' bash-3.2$ /usr/sfw/bin/python Python 2.4.4 (#1, Jul 14 2008, 05:18:49) [C] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> q Traceback (most recent call last): File "<stdin>", line 1, in ? NameError: name 'q' is not defined >>> q Traceback (most recent call last): File "<stdin>", line 1, in ? NameError: name 'q' is not defined >>> quit > Martin:If you send me your pkgdef I can maintain then and > improve/clean up other things such as CFLAGS or whatever, and when > Alan feels ready about integrating I can push them up myself? > > Regards, > Edward. Edward, I don't understand it. If you want to prepare patches you don't need contributor status at all. You can just do this locally and develop and clean-up suggested patches against the gate. These steps are *always* involved. There is no magic IDE tool which does it for anybody of the fox developers, except the cmd line, which is the best IDE you can imagine. You can anonymously clone the gate, pull from it, update your local ws, and so on. You have vi, gdiff, gsed, cat. Some of the current committers can then test them then, commit them and push. Later you can certainly get gate-access yourself. This is the response to your question, but I think is is obvious, wasn't it? The X11 group has stated, that additional external contributors are very welcome. So just ask. Regards, Martin
