Alan McKinnon wrote:
9G is what the dev reckons is the maximum. This other figure of 4G - what is that? The amount needed by some arb combination on some arb user's machine? That's not a good enough criteria. It's not really the maximum plus one well-defined other. It's is the maximum plus every other possible combination (there is no defined minimal). If it's an issue for you, the solution is simple - keep a copy of the ebuild in your local overlay and edit the space requirements. Keep it up to date and in-sync with the ebuild in the main tree. It means you get to a little extra work, but is preferable to the dev doing a lot of extra work
With a compile that takes as long as LOo does, I'd want the dev to be on the side of caution rather than underestimating it. If the max is 9Gbs, then that is what they should check for. I would much rather the dev do that than for me to get to about 90% of the compile done then get the little message that it is out of space. I wouldn't be "hal" mad but it would sort of tick me off a bit. ;-) Maybe not as bad as /usr on init or using a init thingy either. Still a bit upset tho.
Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
