I just unmasked the vim-7.0_beta package. As I wanted to emerge it portage told me, that app-vim/curcmdmode (is blocking app-editors/vim-7.0_beta). So I did 'emerge -C curcmdmode' then emerged vim-7.0_beta. Next time I did an 'emerge -uDvN world' (before any emerge --sync) it just emerged curcmdmod whithout any problem so I thought the block was fixed. But after syncing the portage tree (20060328), and issueing 'emerge -uDvN world' the blocking issue occured again. So I did it again: 'emerge -C curcmdmode'. And when issued 'emerge -uDvN world' it installed curcmdmode again. It seems strange to me. My emerge --info # emerge --info Portage 2.1_pre7-r1 (default-linux/x86/2005.1, gcc-3.4.6, glibc-2.4-r1, 2.6.16-gentoo i686) ================================================================= System uname: 2.6.16-gentoo i686 Intel(R) Celeron(R) CPU 2.40GHz Gentoo Base System version 1.12.0_pre16 dev-lang/python: 2.3.5, 2.4.2-r1 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer noinfo notitles sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.inf.elte.hu/ http://gentoo.inode.at/ http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="hu_HU" LC_ALL="hu_HU" LINGUAS="hu en" 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="x86 X alsa apm avi bash-completion berkdb bitmap-fonts bzip2 crypt cups curl dbus dri dvd eds emboss encode examples exif flac foomaticdb fortran ftp gdbm gif gphoto2 gpm gstreamer gtk gtk2 hal imagemagick imlib jabber javascript jpeg jpeg2k kde kdexdeltas libg++ libwww mad maildir mbox mikmod mime mng motif mp3 mpeg ncurses nls nptl offensive ogg oggvorbis opengl oss pam pcre pdf pdflib perl pic plotutils png python qt quicktime readline ruby samba sdl sockets spell ssl svg tcpd tidy tiff truetype truetype-fonts type1-fonts unicode usb vorbis win32codecs xface xml2 xv zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_hu linguas_en userland_GNU video_cards_fbdev video_cards_sis video_cards_vesa" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LDFLAGS
Yes, blocks are one way, and there's not really an elegant way of handling this. I'm looking into getting curcmdmode either fixed or removed before vim 7 final.
Looks like curcmdmode is working with vim7 again, so the block's gone now.
Thanks for being this fast.