Closed Bug 799095 Opened 9 years ago Closed 8 years ago

Enable Pymake on Mozilla 17 and ESR17

Categories

(Firefox Build System :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rain1, Unassigned)

References

Details

This is something that Callek and Standard8 would like to do. We need a few patches ported over from 18 for that.
Blocks: 785991
Depending on tracking bug for 19-nov-2012 migration work.  Please unblock if this is incorrect.
Blocks: 786550
sid0, callek: will we have a patch ready this week?
I haven't worked on the pymake stuff directly so if it was me I'd be unlikely to have a patch ready this week. I just know from a releng standpoint (both SeaMonkey and ours) I'd like it.

I am a c-c build peer, so I can [help] review/approve stuff.
Flags: needinfo?(sid.bugzilla)
Ok, so to set expectations:

Current Todo:

* (Comm-* Build Team): Write the build-system patches, get review, approval and land on Gecko 17 comm branch[es]
* (releng) Once above is done, enable pymake on comm-release/gecko17 comm branches

As a SeaMonkey driver, I would be willing/wanting to approve this patch for -release/whatever as soon as it is ready for the branch, but I don't personally have the time to work on this one at the moment. So hoping sid (or someone) can figure it out and get it fixed soon!
Since bug 799095 missed the 17 release, we're going to go ahead without pymake enabled and instead target ESR 17.0.1 and 18.0 mainstream.

We *can* turn it on prior to esr 17.0.1, but its not urgent to do so.
I'm pretty sure all the patches for this have landed. Please turn it on on the buildbot side.
Flags: needinfo?(sid.bugzilla)
The only thing that's probably left is backing out bug 585011. I'm not sure if the backout made it to the 17 branch.
Given that we haven't done this yet, I don't think we ever will. We'll just have to live with GNU make on esr17 until it dies.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.