Re: CVS commit: pkgsrc/textproc/groonga

["OBATA Akio" <obata%lins.jp@localhost>]

On Tue, 25 Feb 2014 22:30:36 +0900, Joerg Sonnenberger 
<joerg%britannica.bec.de@localhost> wrote:

> On Tue, Feb 25, 2014 at 02:44:16PM +0900, OBATA Akio wrote:
> > I'm talking about following...
> > * reduce total maintenance cost
> > * not happened on other than your environment
>
> The problem will affect anyone using clang with 2GB available RAM. The
> limit exists (a) because it is still quite a common issue on slower
> hardware (b) it stops ran-away process from killing the whole build.
>
> > Again, are you really using Groonga?
> > Are you glad to drop optimization for such parts?
>
> No, I don't use it. I do care about time wasted on continued rebuild and
> even more important, time wasted looking through build logs. Given that
> packages often enough change the way they break, it doesn't help anyone
> to keep them broken.

No broken report other than you...even on upstream...except on very poor 
environment...

I feel that your environment is just not good enough to bulk build,
or setting is something wrong to bulk build...

1) currently, there are no way for adapting settings to "poor environments"
2) it is too bad to downgrade its performance even on good enough environments

(this kind of matter should be discussed in other place)
--
OBATA Akio / obata%lins.jp@localhost