"ebuild apache-1.3.24-r1.ebuild install" look at the image dir, its perfect.. now do: "ebuild apache-1.3.24-r1.ebuild package" look at the image dir *and* the generated .tbz2, they're both badly b0rked. ie: the /usr/lib/apache directory is completely empty!!! im _sure_ that this is symlink related, since there are several relative symlinks in /etc/apache/. i suggest whomever tries to fix this carefully look at a corectly created image dir (ebuild apache.ebuild install), then cross reference that with the borkedness in ebuild package. you can reproduce this every single time. emerge --buildpkg b0rks it too. not only that, but portage-1.8.8 borks it too! so theres seems to be a funny symlink handling bug, deep in the guts of portage, that has gone unnoticed for a _long_ _long_ time. this apache package has made it easy to see!
yes there is. while testing the masked libpng-1.2.2, kaali caught that the symlinks were linking back into /var/tmp/portage/image// instead of the equivalent live filesystem counterpart.
OK, will be fixed in 1.9.2. Seemant: This sounds like a problem with that package's "make install", and was not in any way related to the bug I just fixed.
