> YES, i know ff 67.0 is not ESR. But, inevitably these changes will come
> down the pike, and i'm having a bit of trouble finding useful info.
> First: The "Profile per Install" really screws me up, as i have an NFS shared
> linux environment where users get firefox via /usr/local/firefox which is a
> symbolic link to /usr/local/firefox-{version} (e.g. firefox-67.0). I use
> autofs automounter also, but the resolved-realpath changes for every release,
> and so the code is going to "help me out" by generating a spankin' new
> Profile for all my users all the time. That's entirely untenable. I've
> updated bug:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1528082
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1528082>
> asking for something more than a proposed Environment Variable (hopefully
> mozilla.cfg admin pref) to keep this from happening.
We have a similar problem in our Windows environment. If you
distribute an application through Microsoft App-V, a new directory is
created for every version based on a GUID.
With the new profile management, this means that every version update
is going to reset your profile because the installation ID will be
different. Some option to disable this feature would be pretty much
required to be able to continue distributing Firefox as an App-V
package.
_______________________________________________
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"
