(In reply to Nick Alexander :nalexander [he/him] from comment #57) > spohl: is your approach to set an extended attribute on the .app bundle? How does that get put in place for distribution? I'm pursuing the same idea for a different use case, and I've got some WIP to our Linux tooling to support extended attributes correctly that might help with this. > > But now I see the attachment marked as obsolete. Can I get some context? I marked the patch as obsolete because this was accidentally submitted to phabricator when I was trying to post the a different patch for bug 1815473. Yes, I intend to set extended attributes for channel-prefs.js and update-settings.ini on the .app. Can you walk me through the "distribution" use case? For the use cases that I'm dealing with, Firefox itself will be setting these attributes since we don't have (and don't want) an installer to fall back on.
Bug 1799332 Comment 58 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Nick Alexander :nalexander [he/him] from comment #57) > spohl: is your approach to set an extended attribute on the .app bundle? How does that get put in place for distribution? I'm pursuing the same idea for a different use case, and I've got some WIP to our Linux tooling to support extended attributes correctly that might help with this. > > But now I see the attachment marked as obsolete. Can I get some context? I marked the patch as obsolete because this was accidentally submitted to phabricator when I was trying to post a different patch for bug 1815473. Yes, I intend to set extended attributes for channel-prefs.js and update-settings.ini on the .app. Can you walk me through the "distribution" use case? For the use cases that I'm dealing with, Firefox itself will be setting these attributes since we don't have (and don't want) an installer to fall back on.