Release MozillaBuild 1.5

RESOLVED FIXED

Status

Product:
mozilla.org
Component:
MozillaBuild
Status:
RESOLVED FIXED
Reported:
9 years ago
Modified:
6 years ago

People

(Reporter: ted, Assigned: ted)

Tracking

Details
(Assignee)

Description

•
9 years ago 
We need a new version of MozillaBuild to pick up a new version of Hg, among other things.

Updated

•
9 years ago
Depends on: 505842

Comment 1

•
9 years ago 
YASM should be on this list too, right?
 (Assignee)

Comment 2

•
9 years ago 
Yes, apparently that bug never got filed.
Depends on: 570477

Comment 3

•
9 years ago 
AFAICT, there's no file in a mozilla-build install that actually tells which version you're having, right? Could we add a VERSION in the root dir or something?
Depends on: 409455
 (Assignee)

Comment 4

•
9 years ago 
We could, sure. I'd just have to remember to update it. :)
No longer depends on: 570477
Depends on: 504994

Comment 5

•
9 years ago 
Can we put yasm.exe into MozillaBuild?

To make the webm build to work for Windows 64-bit I had to:
* wget http://www.tortall.net/projects/yasm/releases/vsyasm-1.0.1-win64.zip
* unzip vsyasm-1.0.1-win64.zip
* mv vsyasm.exe /d/mozilla-build/msys/bin/yasm.exe

I didn't necessarily have to put it in mozilla-build but just somewhere included in the PATH.
 (Assignee)

Comment 6

•
9 years ago 
Armen, see bug 570477.

Comment 7

•
9 years ago 
Ted, when are you planning on wrapping this up? I'll put a patch together for adding WiX and ust want to make sure I finish it in time.
 (Assignee)

Comment 8

•
9 years ago 
I think I'd like to start on this next week just to get it out of the way. (I haven't done anything yet.)
Depends on: 578584

Comment 11

•
9 years ago 
Do you think we could take this change as well?
bug 579159
 (Assignee)

Comment 12

•
9 years ago 
I haven't heard any negative feedback, so I'm going to call rc1 final. (That might be a first!)

Sorry, I'm not going to do another round of builds, even to take trivial patches.
No longer depends on: 578584
Depends on: 581131
You need to log in before you can comment on or make changes to this bug.