On 31 Jul, Neil Bothwick wrote: > On Fri, 31 Jul 2009 09:59:02 +0200 (CEST), Helmut Jarausch wrote: > >> I've done so in the past but I've made bad experience. >> Unfortunately portage isn't so clever, yet. > > portage is a lot cleverer than it used to be, especially with regard to > blocks.
Yes, I'm using portage-2.2_rc33 but still ... > >> Many times (on the 'clones', as well) I had to block packages before >> emerge and then unblock again. I even had to unmerge some packages >> temporarily and emerge them later on again. > > It sounds like you were using -K rather than -k or trying to build binary > packages with --buildpkgonly, which is doomed to failure when trying to > build dependent packages. No, on the 'master' machine I have in /etc/make.conf FEATURES="buildpkg -stricter" and on the clones I use '-k'. But still, portage checks dependencies on the clone. And, if it sees a problem (like those when upgrading to kde-4 or qt-4.5.x) it refused to merge the binary package. Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
