I currently have rss-glx-0.7.4-r1 emerged. I do not want any kde packages so, as part of my USE flags I have '-kde'. Overnight a new version of rss-glx has been marked stable (rss-glx-0.7.6). To emerge it requires the emerging kde-env-3-r3. I do not want this package as I do not want any KDE packages, and I would assume that a USE flag of '-kde' would enforce this. Please modify this package so that if there is '-kde' in the USE flags then kde-env-3 is not a dependency. Reproducible: Always Steps to Reproduce: 1. emerge -up rss-glx Actual Results: These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] kde-base/kde-env-3-r3 [ebuild U ] x11-misc/rss-glx-0.7.6 [0.7.4-r1] Expected Results: These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] x11-misc/rss-glx-0.7.6 [0.7.4-r1] Portage 2.0.50-r11 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.8-gentoo-r3) ================================================================= System uname: 2.6.8-gentoo-r3 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -ffast-math -fomit-frame-pointer -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /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="-march=pentium4 -ffast-math -fomit-frame-pointer -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://www.mirror.ac.uk/mirror/www.ibiblio.org/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo http://ftp.heanet.ie/pub/gentoo/ http://ftp.easynet.nl/mirror/gentoo/ http://mir.zyrianes.net/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm avi berkdb bitmap-fonts bonobo crypt cups encode esd foomatic foomaticdb gdbm gif gimpprint gnome gpm gtk gtk2 gtkhtml imlib java jpeg ldap libg++ libwww mad mikmod mmx mmx2 motif mozilla mpeg mule ncurses nls nptl oggvorbis opengl oss pam pdflib perl png python quicktime readline samba sdl slang spell sse sse2 ssl svga tcltk tcpd tetex truetype x86 xml2 xmms xprint xv zlib"
it's a portage bug really 'fixing' this bug would trigger Bug 43173
Created attachment 40840 [details, diff] Patch to prevent kde-env being installed for non-kde users Any idea why this wouldn't work?
kde-env is just one damn file! why are people so concerned about it? you do realise that even removing that dep, you still will pull kde-env because the ebuild inherits the kde eclass. changing the patch line doesn't do anything either, patches that fix the build process shouldn't be modified conditionally, if anything, to aid testing.
Created attachment 40864 [details, diff] Remove dependency on kde-env Thanks for setting me straight there. This'll be the fix then.
that won't work for the kde users. if you don't inherit kde, you don't get KDEDIR which is what the ebuild relies on for KDE users.
Oh, yes. Then a conditional inherit will work: inherit flag-o-matic eutils if use kde; then inherit kde fi This looks nasty though. I wonder if any other ebuilds have conditional inheritance. Let me know what you think - I know this is a lot of work just for one file, as you say, but it does keep things nice and tidy for non-kde users. At the moment kde-env is just the one file, but who knows what it may contain or depend on in the future.
apparently conditional inherits are frowned upon. i don't know the exact reason why, but it interrupts portge caching or something like that. i suggest that you just give in and not worry about just one file. if you're really that concerned, you can always inject kde-env and be gone with it. i'm going to remove the explict kde-env DEPEND, but not going to modify the inherit kde.
*** Bug 69539 has been marked as a duplicate of this bug. ***