Subject: Re: Overhaul X11 handling [was Re: need advice for integrating
To: None <tech-pkg@NetBSD.org>
From: Jeremy C. Reed <reed@reedmedia.net>
List: tech-pkg
Date: 04/20/2006 10:15:02
On Thu, 20 Apr 2006 joerg@britannica.bec.de wrote:

> > >I plan to kill XFree86 in pkgsrc with the exception of -server, so this
> > >problem will mostly vanish.
> > 
> > If that's really true, then I would certainly not mind seeing the 
> > monolithic X.org packages vanish as well, so that pkgsrc could just 
> > focus on supporting "native-X11" or else using the modular X11 component 
> > packages.
> 
> I don't have strong objections to that as well. I'd like to see a
> two-step approach for that first, though:
> (1) Make it work like native X11 with a symlink package.
> (2) Remove it once the full modular tree is tested and working on all
> platforms Xorg-6.9.0 currently works.

To add some background info about this ...

- The pkgsrc version of XFree86 is way out of date. It is a one release 
behind (as of last year) and will soon be two releases behind. I was going 
to suggest removing it also. If the XFree86-server component is useful, 
then keep it.

- The monolithic X.org is not maintained. I opened a bugzilla ticket to 
track all the suggested fixes for it and others have been adding several 
tickets to it. But nobody has stepped up to be a maintainer of the 
monolithic X.org (which makes sense -- the code is diverging and the build 
environment is all different and so nobody wants to do the same work 
twice).

- The modular X.org needs minor fixes here and there to even support 
DragonFly and NetBSD. (Yes, its ancestor works fine, but in the move to 
modular minor things have changed.) We needed testers for this.

- I have many more packages to do in pkgsrc-wip. There are many packages 
related to modular X.org so it is a little overwhelming. (In fact, I am 
thinking of just scripting the download of all the components source 
tarballs, figuring out the pkg-config dependencies and automatically 
generating pkgsrc directories for each.) In the long run, it will be 
easier to maintain since we will only update the individual components as 
needed. For example, the new X.org will come out soon, but probably 95% of 
the packages (modular X.org components) it depends on never changed.

- In my pkgsrc, I added a X11_TYPE=modular-xorg which uses depends on 
pkgsrc-wip/modular-xorg-libs. I have used this to build and use a lot of 
GTK and QT based software.

- I have not used the modular Xorg "server" components on NetBSD or 
DragonFly yet.


 Jeremy C. Reed

echo '9,J8HD,fDGG8B@?:536FC5=8@I;C5?@H5B0D@5GBIELD54DL>@8L?:5GDEJ8LDG1' |\
sed ss,s50EBsg | tr 0-M 'p.wBt SgiIlxmLhan:o,erDsduv/cyP'