Closed Bug 1070836 Opened 11 years ago Closed 11 years ago

Consider moving prefs files from Contents/MacOS/defaults/ to Contents/Resources/defaults/ on app update

Categories

(Toolkit :: Application Update, defect)

Product:
Toolkit
Component:
Application Update
Platform:
All
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: robert.strong.bugs, Assigned: robert.strong.bugs)

References

Details

When updating to a build with the v2 signing changes we should consider moving the pref files for admin installations. Once issue is that it isn't obvious how to handle an admin install locked with a cfg file so it might be best to punt on this and require reconfiguring the install.
Summary: Consider moving prefs files from Contents/MacOS/default/ to Contents/Resources/default/ on app update → Consider moving prefs files from Contents/MacOS/defaults/ to Contents/Resources/defaults/ on app update
Benjamin, what's your opinion on whether this bug should be fixed. It isn't a problem to move the files but it would be difficult to also move a config file if one was specified. I'm tempted to wontfix this, have a release note, and require admin installs to re-add the files.
Flags: needinfo?(benjamin)
Since Contents/Resources/defaults still requires a new signature, I don't see any value in doing this move. I recommend WONTFIX.
Flags: needinfo?(benjamin)
Signatures are currently only checked on first run. I'm going to go with WONTFIX due to the other reasons but if you disagree please reopen.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.