dhcpcd should be able to be unmerged [ ddicks@linuxbox ~ ] $ qpkg -q -vv net-misc/dhcpcd net-misc/dhcpcd-1.3.22_p4-r4 * /var/db/pkg/net-misc/dhcpcd-1.3.22_p4-r4/dhcpcd-1.3.22_p4-r4.ebuild DEPENDED ON BY: SYSTEM PROFILE net-misc/dhcpcd-1.3.22_p4-r5 /usr/portage/net-misc/dhcpcd/dhcpcd-1.3.22_p4-r5.ebuild DEPENDED ON BY: SYSTEM PROFILE net-misc/dhcpcd-1.3.22_p4-r4 /usr/portage/net-misc/dhcpcd/dhcpcd-1.3.22_p4-r4.ebuild DEPENDED ON BY: SYSTEM PROFILE I know I can inject it but I'd like to be able to remove it totally. Is there any way to add a -dhcp USE to portage so people who do not use dhcp don't have to have dhcpcd?
+1 for this bug. I am also concerned that this bug may indicate a deeper dependency management problem with portage, since it also wants to emerge app-editors/vi, (marked as a New package, depended-on by nothing) which I have never emerged and don't need (having vim).
We're working on it, actually. Currently, we have that all the dhcp clients PROVIDE a virtual/dhcpc. The next step, which is what Aron is working on, will be to make sure the net.ethX scripts can handle different clients. After that we'll be able to implement virtual/dhcpc properly. If all this is fixed before Gentoo's 2004.1 release in 6 weeks, then the base system profile will not include virtual/dhcpc (in other words, a dhcp client will not always be required, it will only be required for those who need it).
Excellent. Thanks!
(Dammit, can't you guys wrap your lines? 8) ) As for vi, check virtual/editor in /var/cache/edb/virtuals
cascading profiles handle this for sure
