and it is really worth to declare that this thing needs about 2 GB to build
I would assume that most people building chromium have more than 2 GB free; that's really not a very large footprint. The exception would probably be people building on tmpfs, but then we have the memory issue to deal with as well. I'm not opposed to adding a disk space check, but I don't really see a significant benefit to it either.
(In reply to Mike Gilbert from comment #1) > > The exception would probably be people building on tmpfs, but then we have > the memory issue to deal with as well. FWIW the background: - at my tinderbox I spent 8 GB for a tmpfs for /var/tmp/portage - shared among - currently - 5 chroot images. So I' do care for packages using significantly more than 2 GB.
04 Mar 2015; Pawel Hajdan jr -chromium-42.0.2305.3.ebuild, +chromium-42.0.2311.15.ebuild: Dev channel bump. Fix bug #541816 by Toralf Foerster. Remove old. I plan to keep the bug open until the fix makes it to stable.
42 is now stable, closing