Closed Bug 842760 Opened 11 years ago Closed 9 years ago

l10n builds should not build in the source directory

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: gps, Unassigned)

References

Details

According to discussion in bug 241047 we currently perform l10n builds in the source directory. We should change it so they build in their own object directory.
Component: Build Config → Release Engineering: Automation (General)
Product: Core → mozilla.org
QA Contact: catlee
Version: Trunk → other
Product: mozilla.org → Release Engineering
Coop: Is this on your roadmap? It's a horrible thing we do and this results in badness like bug 927143.
Flags: needinfo?(coop)
(In reply to Gregory Szorc [:gps] from comment #1)
> Coop: Is this on your roadmap? It's a horrible thing we do and this results
> in badness like bug 927143.

It's known to be terrible, if that's what you mean.

The current l10n repack process is a amalgam of past hacks contributed by bunch of non-build system people to get l10n repacks working. The 2 week delay with release repacks in August is proof of how broken the system still is. Even simple changes are hard right now.

Massimo is working on bug 740142 to port the current l10n repack process to mozharness. I think that is the proper place to make process changes once all the steps are clearly laid out in a single script.
Flags: needinfo?(coop)
The mozharness script sets MOZ_OBJDIR=obj-l10n
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Blocks: 1249441
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.