On Fri, Oct 23, 2015 at 11:39 PM, Jonas Sicking <jo...@sicking.cc> wrote:

> On Fri, Oct 23, 2015 at 3:11 PM, Gregory Szorc <g...@mozilla.com> wrote:
> >
> > We'll be investing pretty heavily in the Firefox build system in 2016. I
> > cannot stress enough the pain comm-central's existence as a separate
> > repository gives us when trying to make build system, mach, and
> automation
> > changes. It slows us down and makes our lives (and code!) more painful
> than
> > they could be.
>
> Can this be solved without migrating c-c into m-c?
>

Would it be possible to create a thunderbird build system which simply
> takes the output of a firefox build and grabs the files that it needs,
> and builds the additions that thunderbird needs.
>
>
Given enough time and resources, c-c's build system could be overhauled.
But as it literally uses mozilla-central's build system and is intricately
tied to it, this effort is roughly equatable with overhauling m-c's build
system. i.e. not trivial. As build module owner, it is my opinion that it
is an easier path to incrementally move both build system's to the future
when they are in one repository.

If we (m-c build peers) didn't care about comm-central at all, I can pretty
much guarantee that comm-central would be perpetually broken once m-c build
system improvements ramp up in the months ahead. C-c's contributors would
have to spend an inordinate amount of time trying to keep pace with m-c
changes.


> Generally speaking, libraries don't worry about having a build system
> which enables building all downstream products. It's the
> responsibility of downstream products to trigger the build system of
> libraries.
>

> The goal of putting seamonkey and thunderbird in separate trees has
> always been to make firefox development easier, not harder. That
> should include the build system.
>

I wish I could join you in the ivory tower. But we have 10+ years of
technical debt in the build system(s) we're working against. If things were
easy, they would have been fixed already.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to