The slots for openbox-2.3.1 and openbox-3.x allows them to be installed together. This is not a good idea, since both install the openbox executeable into /usr/bin. Reproducible: Always Steps to Reproduce: 1. emerge =x11-wm/openbox-2.3.1 2. emerge =x11-wm/openbox-3.1 Actual Results: Both versions are listed as installed (according to epm), even though only openbox-3.1 is usable. Expected Results: Either openbox-3.x should refuse to install if openbox < 3.0 is installed, or it should use the same slot, so that it would automatically upgrade 2.3.1 to 3.1. The argument for refusing installation would be that the configuration file format and location has changed drasticly between 2.3.1 and 3.0. So users running with 2.3.1 are likely not interested in newer versions unless they explictly choose so. Portage 2.0.50_pre16 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20031222-r0, 2.6.1-mm2) ================================================================= System uname: 2.6.1-mm2 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.3.12 Autoconf: sys-devel/autoconf-2.59 Automake: sys-devel/automake-1.7.8 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS=" -z combreloc -mcpu=athlon-tbird -march=athlon-tbird -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS=" -z combreloc -mcpu=athlon-tbird -march=athlon-tbird -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache fixpackages sandbox" GENTOO_MIRRORS="ftp://gentoo.linux.no/pub/gentoo/ http://gentoo.oregonstate.edu http://www.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.gentoo.org/gentoo-portage" USE="X aalib alsa apm arts avi berkdb bonobo cdr crypt cups directfb dvd encode esd fbcon foomaticdb gdbm ggi gif gnome gpm gstreamer gtk gtk2 gtkhtml guile imlib java jpeg kde libg++ libwww mad matrox mikmod mmx motif mozilla mpeg ncurses ntpl oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcltk tcpd tetex truetype x86 xml2 xmms xv zlib video_cards_matrox video_cards_radeon"
I suggest you unmerge openbox-2.3.1. I don't see any pressing reason to revert the slot.
Moving the slot back would cause larger problems IMO, closing the bug.
I don't know about slots, but the bug (i.e. both versions install their main executable as /usr/bin/openbox) still needs fixing. How about installing ob3 as /usr/bin/openbox-3? Until there are automagic tools for migrating the configuration files (i.e. ob2/epist rc/menu) and not just the themes, users who "accidentally" (e.g. via emerge -Du world) upgrade to ob3 experience the shock of their desktops not working as expected. Unfortunately, unmerging ob3 breaks ob2. Of course, that's relatively easily fixed by remerging ob2, but I'd personally much prefer a proactive approach which avoids parallel ebuilds overwriting each other's files.
