If you install 'coldplug' like the handbook proposes and if you try after it 'emerge --update', you will get 'blocked packages'. Reproducible: Always Steps to Reproduce: 1.Installing of gentoo step by step like the book proposes til the point coldplug 2.emerge coldplug 3.emerge --update --ask
You should have read the warnings about not needing to do it if you're on udev-103 and higher. It has not been stabled yet for all arches, therefore the warning is still in place. Also, if you don't immediately update on x86, you can still emerge coldplug without problems. Not a bug, closing.
Josh, it's a networkless handbook. Most users reading it are probably on an arch that has udev-103 in stable tree. Wouldn't it make more sense to use such settings that work for most people in the best possible way? It doesn't make much sense to say "please do foo if you like it to work. Oh, but don't do it in case the current year is >= 2007, otherwise your kitten will die"...
Nowhere in the handbook is the user told to run emerge --update on his system. At this point, the user should not be updating packages; we already have a very clear warning about not needing to install coldplug if the user actually wants to upgrade to udev-103. IMO it's a good thing there is a blocker at this point. If a user starts adding fresh packages into an older system snapshot, bad things can come about -- like trying to add a new udev; that can't be good for booting. There is no way that a user can follow a networkless handbook and run emerge --update in the middle of it. You either follow the networked or the networked directions; you're not supposed to mix those procedures. At the time of writing, udev-103 was not stable on any arch, so that goes double for the networkless handbook. Updating is only supposed to be done *after* installing and rebooting into your system. At that point, the user should follow the Portage Handbook on dealing with blocking packages. Thanks to jkt for discussing on IRC.
(In reply to comment #3) > There is no way that a user can follow a networkless handbook Mea culpa, I meant "networked", not "networkless" :).
