Re: How do you hack on GNOME? How can we do better?

[Steven Harms <sjharms gmail com>]

For what it's worth, I appreciate this discussion taking place on this
mailing list.  As someone who follows the project and wants to get
involved, I have seen and experienced many of the challenges being
discussed.  The energy and expertise around trying to come up with a
solution is exciting to see and I hope this will result in opening the
doors to more developers being able to jump in.

I know it's off topic, but I thought it was worth noting the impact
which often goes unspoken.

Thanks!

Steve

On Tue, Jul 21, 2015 at 8:38 AM, Colin Walters <walters verbum org> wrote:
> On Mon, Jul 20, 2015, at 10:40 PM, Owen Taylor wrote:
>
> > And some of the things that were done to make gnome
> > -continuous robust - like assembling a build root from scratch for each
> > build and building each module from scratch - make it much slower and
> > more resource intensive for local hacking than jhbuild.
>
> I think buildroots quite fast to construct because they use hardlinking
> rather than the IO intensive traditional package manager install.  On my
> home server (SSD) it's 5-10 seconds - and most importantly, it's
> cached - if none of the previous components changed, it's directly
> reused.
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list