The nvu startup script, located at /usr/bin/nvu, looks for the MOZILLA_FIVE_HOME environment variable to determine the location of its binary files. On any system which has this variable in its startup environment, nvu will fail to launch. Reproducible: Always Steps to Reproduce: This problem appears to occur when a system at one time had an older version of the mozilla-suite installed, or if the user had installed, at any time, a binary distirbution outside of portage and hardcoted MOZILLA_FIVE_HOME in the startup environment. Possible ways to resolve this issue: 1) Update mozilla-launcher to include nvu support. 2) Create a custom version of mozilla-launcher, and wrap this around the nvu launch script. 3) Edit /usr/bin/nvu and hardcode MOZILLA_FIVE_HOME. ---------Emerge Info follows------------- Portage 2.0.51_rc9 (!/var/lib/portage/profiles/default-x86-2004.2, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.8.1-ck8 i686) ================================================================= System uname: 2.6.8.1-ck8 i686 Intel(R) Pentium(R) 4 Mobile CPU 1.60GHz Gentoo Base System version 1.6.1 distcc 2.17 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /etc/tomcat5 /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/lib/jboss /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://gentoo.llarian.net/ http://gentoo.binarycompass.org" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/overlays/bmg-gnome-current /usr/local/overlays/bmg-main /usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acpi alsa apache2 arts avi berkdb bindist bitmap-fonts bonobo cdr crypt cups curl dga directfb dnd dv dvd encode esd ethereal evo f77 fastcgi fbcon flac flash foomaticdb gd gdbm gif gimp gimpprintgnome gphoto2 gpm gstreamer gtk gtk2 guile imap imlib innodb java javascript jikes joystick jpeg kde ldap libwww mad maildir memlimit mikmod mmx motif mozilla mpeg mysql ncurses nls noapm nptl odbc oggvorbis opengl oss pam pcmcia pda pdflib perl png pnp python qt quicktime radeon readline ruby samba sasl sdl slang slp speedo spell sse ssl svga tcltk tcpd tetex tiff truetype trusted type1 usb wmf x86 xinerama xml xml2 xmms xprint xv zeo zlib video_cards_radeon"
Looking at the situation, the fix seems pretty straightforward. I'm going to wait for a bit to talk to the other mozilla herd members to verify something quickly.
Ok, I pretty much patched the output file (nvu) before the installation occurs. It will now honor the actual /usr/lib/nvu directory as the correct location for nvu since we don't install it in /usr/lib/mozilla or anything else for that matter. I'm testing the actual ebuild itself and should have that ready by tommorow morning. I had a couple of other tweaks to take care of so the lib directories would be something more standard (/usr/lib/nvu v. /usr/lib/nvu-0.17+), making it easier to transition a couple of things to future versions. So that's basically what the status is :).
Modified nvu-0.50 in portage which uses an nvu patch. This should fix your issue. Also modified a few somewhat non-standard directory structures.
