Hi. # emerge --pretend --update world ... [ebuild U ] net-www/apache-2.0.43-r1 But when it's done, the 1.3.27 is still there, and protected from emerge clean. I don't need apache2, why it always wants to khm, "upgrade" my 1.3.27?
apache 1.x and apache 2.x can both be installed and utilized at the same time
Yes, but there is no need for _upgrade_ from 1.3.27 to 2.0.43, and it's not an upgrade: it's in fact two package with the same purpose (webserver). but after 'emerge --update world' there is 2 protected apache in my system, and if i remove apache-2.0.43-r1, the next world update put it back again, meanwhile my apache1 is untouched.
actually, it *is* an upgrade ... if you *really* dont want 2.x, then just inject it `emerge inject net-www/apache-2.0.43-r1`