I currentely have a problem on my system where X and some related applications do not build. The problem is that portage has not detected that something wrong was going on. For example, when I build tightvnc, portage installs the perl scripts vncserver, vncviewer, vncpasswd and vncconnect but not the Xvnc file, because for some reasons, it could not build it. It installed all this without noticing that some file were missing from the installation. What I suggest is to provide in the ebuild a file list of the files that are expected to be install. This could be a detailed list of all files, a list of some important files or just the number of files to be installed. At least it would track my problem sooner. It is very important to provide some security checks at every step of using portage. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Wouldn't that be huge to maintain? Furthermore, USE settings might influance the number of files installed. I really think it's almost impossible. we would get rpm like stuff and that's the reasing i'm using Gentoo, to not deal with that. However if you ask me the correct behaviour should be that if part of this package's make process fails, the emerging should fail. That is probably a problem with tightvnc.
yes, that would be too much of a load to maintain if tightvnc failed please make a bug about such a problem
