Using the following use flags: [ebuild R ] app-office/openoffice-3.0.1 USE="cups dbus java kde nsplugin opengl pam -binfilter -debug -eds -gnome -gstreamer -gtk -ldap -mono -odk -templates" LINGUAS="en_US -af ..." # (no other languages selected) emerging used 5.3G of disk space in /var/tmp/portage. The ebuild does mention that "4-6 GB free diskspace and 256 MB RAM are the minimum requirements", but it only checks for 5G, instilling false confidence in those who have 5G or more of free disk space but less than the actual required amount. If you're not convinced that this is a problem, here's my reasoning: It might not be the ebuild's responsibility to check for sufficient free disk space, but if it's going to check, it should check for the UPPER LIMIT of needed free disk space. Since all it does in cases where free disk space is less than the checked-for amount is warn you that you might not have enough, passing the requirements should mean that you definitely have enough. Also, I did see this other bug: http://bugs.gentoo.org/show_bug.cgi?id=249255 but I don't think this is a duplicate, because that one was about building with debugging symbols enabled. Thanks!
Yeah, the build doesn't get smaller over time. Raised the limit to 6 Gig now, thanks for reporting!
(In reply to comment #1) > Yeah, the build doesn't get smaller over time. Raised the limit to 6 Gig now, > thanks for reporting! > Awesome, thanks!
