When installing lilypond on my headless server system it tries to install xterm and xorg. Reproducible: Always Steps to Reproduce: 1. emerge app-text/mftrace -vp -e -tree Actual Results: [snip] [ebuild N ] x11-terms/xterm-197 -Xaw3d -debug +truetype -unicode 674 kB [ebuild N ] sys-apps/utempter-0.5.5.5-r1 -debug 20 kB [ebuild N ] app-arch/rpm2targz-9.0-r2 2 kB [ebuild N ] app-arch/cpio-2.6-r1 +nls 437 kB [ebuild N ] sys-apps/which-2.16 122 kB [ebuild N ] sys-apps/file-4.12 -build -debug +python 404 kB [ebuild N ] sys-devel/gcc-config-1.3.8-r4 0 kB [ebuild N ] sys-apps/portage-2.0.51.19 -build -debug (-selinux) 277 kB [ebuild N ] dev-lang/python-2.3.4-r1 +X +berkdb -bootstrap -build - debug -doc +gdbm +ipv6 +ncurses +readline +ssl +tcltk -ucs2 7,020 kB [ebuild N ] dev-lang/tk-8.4.6-r1 -threads 3,155 kB [ebuild N ] x11-base/xorg-x11-6.8.2-r1 -3dfx -3dnow +bitmap-fonts -cjk -debug -dlloader -dmx -doc +font-server -hardened -insecure-drivers +ipv6 - minimal -mmx +nls +opengl +pam -sdk -sse -static +truetype-fonts +type1-fonts (- uclibc) -xprint +xv 45,105 kB [/snip] Expected Results: No dependency on xorg. I actually just edited the ebuild in /usr/portage as I just wanted to try out lilypond. I did not notice any misbehaviour. Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20041102-r1, 2.6.9-gentoo-r13 i686) ================================================================= System uname: 2.6.9-gentoo-r13 i686 Intel(R) Pentium(R) III CPU family 1266 MHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 8 2005, 11:12:54) ] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r3, 1.5, 1.7.9-r1, 1.6.3, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.4.22-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=i686 -mcpu=i686 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/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/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -mcpu=i686 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/" 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 apache2 avi berkdb bitmap-fonts crypt curl emboss encode fam flac flash font-server foomaticdb fortran gd gd-external gdbm gif gtk2 guile hardenedphp imagemagick imap innodb jpeg ldap libwww mad maildir md5sum mp3 mpeg mysql ncurses nls no-htdocs oggvorbis opengl pam pam-mysql pdflib perl php png postgres python quicktime readline ruby samba sasl sdl se slang spell sqlite ssl tcpd tetex tiff truetype truetype-fonts type1-fonts vhosts xml xml2 zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
mftrace depends on python which is about to be built. Your emerge tree shows python being built with the +X useflag, so it depends on X. put "-X" in your use flags so that python doesn't depend on X, and all should be well.
old
