every program linked to libdirectfb-09.so.19 (installed with directfb-0.9.19*) is broken after an update to directfb-0.9.20 because the libs of older versions were removed. a revdep-rebuild fixed everything for me, but maybe some people experience the same problem. emerge info: Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r8, 2.4.20-wolk4.10s) ================================================================= System uname: 2.4.20-wolk4.10s i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.3.11 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-tbird -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-tbird -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt encode gif jpeg libg++ libwww mad mikmod motif mpeg ncurses nls pdflib png spell truetype xml2 xmms xv zlib alsa gdbm berkdb slang readline svga X sdl gpm tcpd pam ssl perl python esd imlib oggvorbis gtk opengl 3dnow canna cjk directfb dvd etwin fbcon fbdev gd gtk2 gtkhtml java jikes joystick js ladcca mldonkeypango mmx openssh samba socks5 tiff xchattext xface xine xinerama -arts -cups -foomaticdb -kde -gnome -qt -quicktime"
known issue ... DirectFB maintainers claim no compatibility between 0.9.x releases ... i added a warning message to use revdep-rebuild at the end of directfb merge
Is there a way to "freeze" directfb? I have a few libs that were built with directfb support and if I miss a directfb upgrade during a "world" upgrade then I may end up spending hours and hours with revdep-rebuild, which doesn't always work just right (the recent libsdl issue for example). I've already stopped using programs like qingy (login program that depends on directfb) because it was dangerous to have a program depend on directfb that might suddenly break. Directfb really needs some special treatment I think since it can break so many programs. A "version freeze" is really needed, and perhaps revdep-rebuild should be added to the ebuild, and a warning requiring user-interaction to actually upgrade an existing directfb. Either that or put every release of directfb in its own slot so that old versions are always there, or better yet, just statically link directfb so that the libs can be upgraded as much as you want - remerging old apps would then upgrade them to the new directfb but they would still work with the old directfb if you didn't remerge them. Is there some way to tell portage that I want directfb to only be a static library? I'll do it right now if I could. Some of us have slow computers and don't want to upgrade tons of apps that worked yesterday just because a new directfb got pulled in!
