Currently as long as SNAP_NAME is defined to something it will disable profiles-per-install, but there is an intention to replace that method of detecting snap packaged so I can't guarantee that that will exist long-term.
On Thu, May 30, 2019 at 3:50 AM James Pearson <[email protected]> wrote: > Dave Townsend wrote: > > > > (sorry if this doesn't thread right, I only just joined this list) > > > > Regarding how the dedicated profiles per install feature works, there > > is currently no difference between how it works on normal Firefox > > builds and ESR. > > > > New versions of Firefox are not new installations. The installation > > is defined by the installation directory. > > > > As long as you are upgrading the Firefox version by putting the new > > version into the same directory that the old version was in then > > users would continue to use the same profile. We are currently seeing > > an edge case where that is breaking right now on Windows but I'm > > expecting to have that fixed before Firefox 68 ships. > > > > There is currently no policy setting to disable this feature, there > > is currently an environment variable that can be set (though it's > > targeted at a different use case right now, so if important I'd like > > to use a different name for it) but it applies to any version and > > channel of Firefox. > What is the environment variable and what does it need to be set to for > disabling dedicated profiles ? > > Thanks > > James Pearson
_______________________________________________ Enterprise mailing list [email protected] https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected] with a subject of "unsubscribe"
