Closed Bug 1048921 Opened 7 years ago Closed 7 years ago

figure out how to transform mac builds from old style -> new style in mars

Categories

(Release Engineering :: Custom Release Requests, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

References

Details

After bug 1047738 lands, we'll be putting distribution/ in .app/MozResources rather than .app/Contents/MacOS/distribution. We'll also be moving channel-prefs.js. Neither of these files is normally touched by a mar, so we'll need to do something special to rearrange them.

Is there some way we can move existing files around, without shipping new contents?
Flags: needinfo?(robert.strong.bugs)
Flags: needinfo?(nthomas)
channel-prefs.js will be handled in bug 1047728 and will be handled using our current capabilities in the updater.

A solution for distribution/ will need to be developed and though I haven't decided on a solution we'll come up with something.
Flags: needinfo?(robert.strong.bugs)
Smells a like a "MOVE-IF <source> <destination>" instruction added to the updater. Such a thing would require a watershed, to get an updater on disk that understands the new instruction (ie got to ship support in a release, and use it in the next one).  Or maybe a post-update task hardcoded into the app, which wouldn't need a watershed. I'll stop trespassing on rstrong's patch now.

There are too many partners & variations for us to build & test custom mar files IMO.
Flags: needinfo?(nthomas)
(In reply to Nick Thomas [:nthomas] from comment #2)
> Smells a like a "MOVE-IF <source> <destination>" instruction added to the
> updater. Such a thing would require a watershed, to get an updater on disk
> that understands the new instruction (ie got to ship support in a release,
> and use it in the next one).  Or maybe a post-update task hardcoded into the
> app, which wouldn't need a watershed. I'll stop trespassing on rstrong's
> patch now.
Agreed on both scores. I haven't decided on which path to take and feel free to "trespass"!

> There are too many partners & variations for us to build & test custom mar
> files IMO.
Agreed wholeheartedly and I wouldn't do that to you guys.
11:47 <@bhearsum> rstrong: does https://bugzilla.mozilla.org/show_bug.cgi?id=1048921 need to be addressed still?
11:48 < rstrong> bhearsum: no... it is already handled
11:48 <@bhearsum> ah, ok
11:48 <@bhearsum> is it a WONTFIX then?
11:48 < rstrong> bhearsum: sure
11:48 <@bhearsum> thanks!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.