On 11/08/13 21:13, Neil Bothwick wrote:
On Sun, 11 Aug 2013 11:52:26 -0400, Tanstaafl wrote:
but the issue here was eudev *not* being updated when the virtual
was, and both cause and result were quite clear.
Right, but I was talking about not updating *anything* related to any
mission critical apps, and that would include the virtual/udev as well.
That said - shouldn't this be taken care of by the the virtual/udev
package itself? Shoudln't it keep track of what versions of udev *and*
eudev it supports, and warn you (via a [B]blocker)?
There was a blocker (small b) because virtual/udev needed sys-fs/udev and
that gave a blocker that uninstalled eudev.
I believe it's 'b' if user doesn't have sys-fs/eudev in
/var/lib/portage/world, but 'B' if he does
As in, difference is soft and hard blocker depending if the wanted
implementation is recorded in the world file or not
