can you guys make xfree86 and fcpackage be seperate ebuilds? or at least leave the xft that comes with xfree alone, and install xft2 to a different directory. What I suggest is: configure xft2 ( from fcpackage) with: ./configure --sysconfdir=/etc --prefix=/usr/X11R6 --includedir=/usr/X11R6/include/Xft2 and leave the default xfree86 xft(1) headers in /usr/X11R6/include/X11/Xft!!! that way any program wanting xft1 will find the headers. and any program wanting xft2 will use `xft-config --cflags` to get the proper headers (eg -I/usr/X11R6/include/Xft2) the way it is now, just doesnt make sense. thank you for considering this.
Please make sure of you facts, or at least make the effort to read the ebuild and at least make some sense of it *before* you make comments. Xft-2.0 *is* a seperate package, in x11-libs/xft. That which was included with xfree was only the updated Xrenderer, and Xft-1.2 (NOT 2.0).
I did read the ebuild... and I saw this... S_XFT2="${WORKDIR}/fcpackage.${FC2_VER/\./_}/Xft" guess I didnt read it too close. why is this line even in the ebuild? but anyway, I dont think you guys should update _anything_ from fcpackage to replace native xfree stuff. I guess im the only one that thinks this, so i will continue to compile x without an ebuild :-(.
So I guess we also should not update the savage, sis and wacom driver ? And what about the patches that enables support for ati radeon 9000 ? And for i830 ?
And while we are on the topic ... you know of course that xfree-4.3.0 will include the stuff in fcpackage by default ?
aha, good idea to not include the wacom and sis drivers, make them like the nvidia-glx ebuild! sorry that im such a picky bastard. cya.
I just though of something: would you consider adding a ebuild called xfree-vanilla-4.2.1.ebuild? I could hack such an ebuild up, if you would add it to portage.
