Hello, If a person, like myself, emerges ut2004, the ebuild will attempt to build the binary package and bzip it up. Considering that the total size of the package is about 5.2 GB, this will take about 2.5 hours - and crash the ebuild - probably due to lack of system memory. ut2004 is already in binary form, so there is no reason to build a binary package. Worse it wastes about two and a half hours trying to bzip it up... before failing. The ut2004 ebuild should override and disable the buildpkg flag in FEATURES. That is all. Reproducible: Always Steps to Reproduce: 1. 2. 3.
You cannot diable a FEATURE from within an ebuild. Turn off buildpkg or run FEATURES=-buildpkg emerge ut2004... There's nothing I can do about this without making a massive extension to portage. Also, it *will* build, provided you have enough RAM+swap, so there's nothing wrong with the ebuild/portage. Technically, it is your machine that is not able to do what is asked of it... ;]
