I noted that the packages sys-apps/iproute2 and net-analyzer/ifstat both provide an implementation of ifstat (1). The sys-apps/iproute2 implementation defaults to /sbin/ifstat and the net-analyzer/ifstat implementation to /usr/bin/ifstat, so that a different implementation is called depending on the users' PATH variable, when you only type ifstat without the full path to the binary. My suggestion is to create a eselect module which gives lets you choose the default implementation to fix that issue.
I would rather find out if we need the one in net-analyzer/ifstat or if they are fully compatible. If they are, we may be able to have the packages block each other. Two packages that have binaries with the same name shouldn't be able to be installed at the same time.
(In reply to William Hubbs from comment #1) > I would rather find out if we need the one in net-analyzer/ifstat or if > they are fully compatible. > > If they are, we may be able to have the packages block each other. They're not compatible. > Two packages that have binaries with the same name shouldn't be able to > be installed at the same time. They install binaries with the same name to different paths: /sbin/ifstat (sys-apps/iproute2) /usr/bin/ifstat (net-analyzer/ifstat) so they needn't block at all.
