It would be nice if the check behavior could be modified to give the user the option to proceed or not. In the event they have less resources available than what the ebuild feels it needs to build. I regularly run into this with Chromium and Firefox, but might others as more packages add checks. I have never had either of those fail due to not having enough disk space. But I do have less than both require and I am constantly having to edit the ebuilds. It would be nice, if instead of portage failing when the check fails. That it gave me the option to proceed anyway, like at my own risk. Knowing that it might fail, but in my case it most likely will not. That way the checks can remain, and I do not have to keep editing the ebuild. Also for others like me, who have less than required, but enough to build without issue, can proceed just the same :) Thank you for consideration of this request. I so hate this... There is NOT at least 5 GiB disk space at "/tmp/portage/www-client/chromium-49.0.2623.75/temp" ERROR: www-client/chromium-49.0.2623.75::gentoo failed (pretend phase): * Build requirements not met! But I do not need 5GB on my system, I build it just fine all day long with like 4.8GB.
I_KNOW_WHAT_I_AM_DOING=1
