
XGL sucks and is old news.dman777 wrote:Perhaps I may come back to Gentoo some day if I get another system. But I am really disappointed.

There's nothing really fundamentally wrong with it, it's just a little buggy, and the more interesting backend (EGL) seems to have been pretty much abandoned. However, some people seem to have turned against it, now that it isn't the only X server capable of running Compiz.Workaphobia wrote:For my curiosity, what's wrong with XGL, technically speaking (but in low detail)?
< dang> The last time I tried it [pkgcore] (admittedly a while ago) it managed to get my box into a state where it didn't work and portage didn't work.
< dang> I had to re-install the box.
This is what I'm currently using... there are newer versions in upstream's git, but they either didn't work for me or require the unstable version of renderproto. Completely unsupported, use at your own risk, blah blah blah....dman777 wrote:It doesn't matter XGL sucks....because it's my only choice!!!!! It's better than nothing!!!! Why can't that be understood?????????
mod edit: fixed long line --bunderx11-base/xgl/xgl-0.0.1_pre20070530.ebuild wrote:Code: Select all
# Copyright 1999-2008 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: $ SNAPSHOT="yes" inherit flag-o-matic git x-modular multilib XGL_EGIT_REPO_URI="git://anongit.freedesktop.org/git/xorg/xserver" XGL_EGIT_PROJECT="xgl" XGL_EGIT_BRANCH="xgl-0-0-1" XGL_EGIT_TREE="b5271285d159393294279bd26445ac1aa0203227" MESA_EGIT_REPO_URI="git://anongit.freedesktop.org/git/mesa/mesa" MESA_EGIT_PROJECT="mesa" MESA_EGIT_BRANCH="master" MESA_EGIT_TREE="6ca46505363072b628cbc0accc04c6db7e3f53a0" XGL_S="${WORKDIR}/${PN}" MESA_S="${WORKDIR}/mesa" S="${XGL_S}" DESCRIPTION="Xgl X server" HOMEPAGE="http://xorg.freedesktop.org/" SRC_URI="" LICENSE="X11" SLOT="0" KEYWORDS="~x86 ~amd64 ~ppc" IUSE="ipv6 xinerama" DEPEND=">=media-libs/glitz-0.5.6 >=media-libs/mesa-6.5.2_pre20061102 x11-proto/xf86driproto x11-proto/randrproto x11-proto/renderproto >=x11-proto/fixesproto-4.0 x11-proto/damageproto x11-proto/xf86miscproto >=x11-proto/scrnsaverproto-1.1 x11-proto/resourceproto x11-proto/fontsproto x11-proto/xf86dgaproto x11-proto/videoproto >=x11-proto/compositeproto-0.3 x11-proto/trapproto x11-proto/recordproto x11-proto/xineramaproto x11-proto/evieext x11-libs/libXfont x11-libs/libxkbfile x11-libs/libxkbui x11-libs/libXxf86misc" RESTRICT="mirror" pkg_setup() { # (#121394) Causes window corruption filter-flags -fweb CONFIGURE_OPTIONS=" $(use_enable ipv6) $(use_enable xinerama) --enable-xgl --enable-xglx --enable-glx --enable-dri --disable-xorg --disable-aiglx --disable-dmx --disable-xvfb --disable-xnest --disable-xprint --with-mesa-source=${MESA_S} --sysconfdir=/etc/X11 --localstatedir=/var --enable-install-setuid --with-font-dir=/usr/share/fonts --with-default-font-path=/usr/share/fonts/misc,/usr/share/fonts/75dpi, /usr/share/fonts/100dpi,/usr/share/fonts/TTF,/usr/share/fonts/Type1" } # yuck :-( x-modular_unpack_source() { for v in ${!XGL_EGIT_*}; do eval "${v#XGL_}="\${!v}"" done git_src_unpack S="${MESA_S}" for v in ${!MESA_EGIT_*}; do eval "${v#MESA_}="\${!v}"" done git_src_unpack S="${XGL_S}" cd "${S}" } src_install() { x-modular_src_install rm "${D}/usr/share/aclocal/xorg-server.m4" \ "${D}/usr/share/X11/xkb/compiled/README.compiled" \ "${D}/usr/$(get_libdir)/xserver/SecurityPolicy" \ "${D}/usr/$(get_libdir)/pkgconfig/xorg-server.pc" \ "${D}/usr/share/man/man1/Xserver.1" }
< dang> The last time I tried it [pkgcore] (admittedly a while ago) it managed to get my box into a state where it didn't work and portage didn't work.
< dang> I had to re-install the box.


at least the (~)0.0.1_pre20070105 one should work (if I recall right it did for me), after that the others wouldn't compile / work* x11-base/xgl
Available versions: (~)0.0.1_pre20070105[1] (~)0.0.1_pre20070105[2] (~)0.0.1_pre20070727[1] (~)0.0.1_pre20070915[1] (~)0.0.1_pre20070918[1] {ipv6 xinerama}
Homepage: http://xorg.freedesktop.org/
Description: XGL X server
[1] "sabayon" /usr/local/portage/overlay
[2] "xeffects" /usr/local/portage/xeffects
Dude, you flip over one particular piece of eye candy missing on your machine? Chill...dman777 wrote: AND XGL IS NOT STILL AROUND FOR GENTOO. I HAVE ONLY MANAGED TO GET MY HANDS ON TWO VERSIONS. ONE WOULDN'T INSTALL BECAUSE IT COULDN'T FIND A TAR FILE. THE OTHER WOULDN'T INSTALL BECAUSE OF SOME ERROR OF AT THE END OF THE INSTALLATION. SO THEREFORE, THERE IS NO XGL FOR GENTOO! THAT MEANS IF I WANT TO USE GENTOO AND COMPIZ FUSION, I CAN'T!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Yes, unfortunately there's no way to automate it with git, as far as I know. You need to check http://gitweb.freedesktop.org/?p=xorg/x ... =xgl-0-0-1 and http://gitweb.freedesktop.org/?p=mesa/m ... a=shortlog for the commit corresponding to the date that you want, then use the "tree" ID (for example, the latest Xgl commit has a tree of e74732ae116070ceba6e1288dd0ac75976d3c267).dman777 wrote:If I change the ebuild to 20070127 do I also have to change the XGL_EGIT_TREE and MESA_EGIT_TREE lines? And if so, how do I find out what they are?
< dang> The last time I tried it [pkgcore] (admittedly a while ago) it managed to get my box into a state where it didn't work and portage didn't work.
< dang> I had to re-install the box.
http://gentoo-wiki.com/HOWTO_compiz-fusiondman777 wrote:Ok, for my last 4 days off I have been struggling to get Compiz Fusion to run with my ATI VGA card. I have been working 24/7 on those days off trying to get it working. It all comes down to XGL. I can't get it for Gentoo. Why did you take it out of the portage tree, Gentoo? Just because it's a dead product doesn't mean it isn't needed. I can't even get an overlay for it. It's still easly accessible with other linux's, but not Gentoo. I see many other people on here with the same problem as me needing XGL. Perhaps I may come back to Gentoo some day if I get another system. But I am really disappointed.
Code: Select all
LIBGL_ALWAYS_INDIRECT=true compiz --replace ccp &Code: Select all
LIBGL_ALWAYS_INDIRECT=trueCode: Select all
env-updateCode: Select all
compiz --replace ccp &Code: Select all
LIBGL_ALWAYS_INDIRECT=trueCode: Select all
env LIBGL_ALWAYS_INDIRECT=true compiz --replace ccpCode: Select all
WINDOW_MANAGER=/usr/local/bin/compiz-startCode: Select all
# compiz-start script
#
# hacky autodetection of neccessary options for XGL/AIGLX/NVIDIA
#
# Hanno Boeck, http://www.hboeck.de/
#
# Licensed under the same conditions as compiz itself (MIT or GPL)
if [ ! -x /usr/bin/glxinfo ]; then
echo "glxinfo not found, please install mesa-progs."
exit -1
fi
GLX_WITH_DIRECT=`glxinfo|grep -c GLX_EXT_texture_from_pixmap`
GLX_WITH_INDIRECT=`LIBGL_ALWAYS_INDIRECT=1 glxinfo|grep -c GLX_EXT_texture_from_pixmap`
GLX_RENDER=`glxinfo|grep -c "OpenGL renderer string: Mesa GLX Indirect"`
COMPIZ_OPTIONS="--replace ccp --sm-disable"
if [ $GLX_WITH_DIRECT -eq 3 ]; then
if [ $GLX_RENDER -eq 0 ]; then
echo NVIDA detected
export __GL_YIELD="NOTHING"
else
echo XGL detected
fi
elif [ $GLX_WITH_INDIRECT -eq 3 ]; then
echo AIGLX detected
export LIBGL_ALWAYS_INDIRECT=1
fi
if [ ! -z $KDE_FULL_SESSION ] && [ -x /usr/bin/kde-window-decorator ]; then
echo Using KDE decorator
kde-window-decorator --replace &
else
echo Using GTK decorator
gtk-window-decorator --replace &
fi
compiz $COMPIZ_OPTIONS gconf move resize minimize place decoration wobbly fade cube rotate scale switcher zoom dbus
update - "a most excellent portage wrapper"creaker wrote:systemd. It is a really ass pain
you should add the -1 parameter to these types of emerge commands, this will keep them from erroneously being put into your world file. since they are just deps.dman777 wrote:1)The first thing we will do is emerge Cairo.
# emerge --ask --verbose cairo
Rebuild pango and gtk+ against the newly built Cairo package.
# emerge --ask --verbose pango gtk+
2) Emerge Xgl and Mesa:
# emerge --ask --verbose --noreplace mesa
Code: Select all
emerge -1 -av pango gtk+Speaking of which, I've already managed to do this at some point - that is, emerge dependencies without --oneshot, which makes a mess of my world file. My solution was to edit the world file directly (backing up the original), deleting packages which were obviously dependencies and retaining only the packages which I'd explicitly installed. The result was not a series of errors upon a new emerge, but insteadjonnevers wrote: you should add the -1 parameter to these types of emerge commands, this will keep them from erroneously being put into your world file. since they are just deps.
Code: Select all
emerge -1 -av pango gtk+
Code: Select all
emerge -avDuN world1. nah, I don't think so (but perhaps). It's probably taking a closer look because of the extra world entries. I'm interested to see what the two emerge lists look like and how exactly they differ.csteeves wrote:It seems to me that if I had deleted only the dependencies from world, then I should get the same result for both my edited and unedited world files.
1. Is this assumption correct?
2. What would be an appropriate method for repairing a world file cluttered with dependencies?
Thanks.
Craig