war journal 003 - things *not* to do with portage

aaah yes. got the notebook back up and running. installed the system yesterday, then executed an emerge --update --fetchonly world and emerge --deep --fetchonly gnome


then executed emerge --deep gnome and left it running while i was sleeping which is a good idea thing. multithreading is certainly an excellent idea, don't you think?

ok. so i waking up, the machine was running properly and i had endeavored run emerge openoffice-bin (i learned my lesson that compiling oo2 just isn't worth it so getting the bin is much better) then endeavored to update the system by executing an emerge sync followed by an emerge --update world

the machine worked well. so i visited http://arts.gnome.org (i prefer the simplicity of gnome over the complexity of kde, but thats just me) and downloaded some stuff to make my machine look great.

then i started downloading gcc 3.4 and installed it so that i could take advantage of -march=pentium-m but here comes the stupid part--- i unmerged gcc-3.3.6 after executing emerge =gcc-3.4.4-r1

that was pretty stupid! i know! and i'm left with a machine that pretty much runs, but i broke portage. :(

another install down the drain. but the good thing is i'm learning even from these mistakes.

di