I was using galeon 1.3.4 from the portage tree just fine and dandy and I decided, like a dummy, to change it... I emerged in galeon-cvs and it went just fine. I see that /usr/bin/galeon and galeon-bin show today's date so I'm sure it installed them. I decide to roll back so I unmerge galeon-cvs. Fine... good... well /usr/bin/galeon is missing... galeon 1.3.4 is still listed as installed but it's gone. re-emerge galeon 1.3.4 and it's happy again. The short of this is that galeon-cvs should have a "galeon blocks galeon-cvs" flag since they won't co-exist. Reproducible: Always Steps to Reproduce: 1. 'ACCEPT_KEYWORDS=~x86 emerge /usr/portage/net-www/galeon/galeon-1.3.4.ebuild' 2. run galeon, and see it's happy 3. 'ACCEPT_KEYWORDS=~x86 emerge galeon-cvs' 4. see galeon work good 5. 'emerge unmerge galeon-cvs' Actual Results: /usr/bin/galeon doesn't exist. Expected Results: I expected that the galeon-cvs ebuild should have installed the binary as galeon-cvs instead of galon... or that the galeon-cvs ebuild would say that galeon is a blocking package. Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4) ================================================================= System uname: 2.4.20-gentoo-r5 i686 Intel(R) Pentium(R) III Mobile CPU 1000MHz GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo http://csociety-ftp.ecn.purdue.edu/pub/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss 3dnow apm arts avi crypt cups encode gif jpeg libg++ libwww mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gtkhtml alsa gdbm berkdb slang readline bonobo tcltk java guile X sdl gpm tcpd pam ssl perl python esd imlib motif opengl mozilla gnome gtk oggvorbis gtk2 -kde -qt aalib directfb fbcon svga" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O3 -pipe" CXXFLAGS="-O2 -mcpu=i686 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
galeon-cvs and galeon-1.3 occupy the same space, seems sorta obvious. You should know that fooling around with p.masked and ~ unstable stuff can get you into trouble. Should we even make stuff like cvs ebuilds totally foolproof. Anyway i'd say it's time to remove galeon-cvs , we have 1.3 releases. The need is gone.
i agree with removing galeon-cvs. i think galeon releases are now frequent enough and stable enough to be used without having to resort to cvs. if i may guess, this was probably added when galeon did not have a 1.3.x (gtk2) release. now that there are gtk2 releases, it should be removed. any arguments for keeping this in portage?
nope, galeon-cvs is removed
