Although I'm using udev (and having unmerged devfsd), devfsd keeps coming back all the time -- due to the system profile and deps. For us udev users, it would be nice if devfsd would stay unmerged, as it's quite useless. An easy solution would be making device management a virtual (virtual/devfs e.g.) and define devfsd and udev as providers for it. Any suggestions? Reproducible: Always Steps to Reproduce: 1. emerge udev 2. emerge -C devfsd 3. emerge -u system/world Actual Results: devfsd gets emerged Expected Results: evil devfsd should stay away [ ~ ] user@host $ emerge --info Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.3-rc3-love1) ================================================================= System uname: 2.6.3-rc3-love1 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.3.13 Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.7.7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon -O2 -pipe -fomit-frame-pointer -ffast-math -funroll-loops -fforce-addr" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /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/env.d" CXXFLAGS="-march=athlon -O2 -pipe -fomit-frame-pointer -ffast-math -funroll-loops -fforce-addr" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache digest sandbox userpriv usersandbox" GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ http://gentoo.linux.no/ http://www.ibiblio.org/pub/Linux/distributions/gentoo/" 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="3dnow X acl acpi alsa avi berkdb bonobo cdr crypt cups dvd encode esd gif gnome gstreamer gtk2 imlib jikes jpeg libwww mad maildir mmx mpeg mpi ncurses nls oav odbc oggvorbis opengl pam pda pdflib png quicktime readline samba sdl spell ssl tcpd tetex truetype x86 xml2 xv zlib"
# find /usr/portage -name '*.ebuild' -exec grep -H 'sys-fs/devfsd' '{}' \; /usr/portage/app-cdr/cdrw-base/cdrw-base-0.2.ebuild:DEPEND="sys-fs/devfsd" [skipped irrelevant stuff] So, there seems to be only one single package that directly depends on devfsd. Then, we have to modify: - the packages and virtuals file(s) in the profile dirs - the sys-fs/{devfsd|udev} ebuilds - the app-cdr/cdrw-base ebuilds IIRC, the eclasses don't have direct deps on devfsd.
*** Bug 41699 has been marked as a duplicate of this bug. ***
The situation is more complex than just a virtual. Some users do not prefer to activate either devfsd or udev. A complete solution must allow for 1. selection of devfsd, udev, or none starting from stage1,2,3 at install time 2. If none is chosen, populate /dev accordingly 3. Activation of devfsd, udev, or none by the bootscripts
This could be easily solved by providing a third bogus package (sys-bogus/mknod-devfs or something) which does nothing but PROVIDEing virtual/devfs for those who want to use the old (very deprecated) way to manage /dev. Devs, anyone?
This will have to wait until we can figure out how to get both 2.4 and 2.6 to exist in the profile. For now, emerge inject a version bigger than latest.
It looks like this has been fixed recently -- by introducing a virtual for device manangement, as I suggested in the first place. Funny, that... As such, I will close this issue.
