Comment 141 for bug 233901

(In reply to comment #7)
> I've created a guide describing how to setup Autoconfig with Mozilla Firefox.
> Take a look:
> http://mit.edu/~firefox/www/maintainers/autoconfig.html
>
> I also have a brief writeup describing how autoconfig is setup at MIT, and a
> link to the relevant files:
> http://mit.edu/~firefox/www/maintainers/config.html

Charles has done an excellent job here of documenting the baroque Mozilla
configuration process. But it would be much better if the software was changed
so that much of the complexity vanished. For example:
(1) The configuration file should not have to reside in the software directory,
because that way it is highly likely to get lost or overwritten whenever the
software is upgraded. Instead the software should follow Unix FHS standards and
look in /etc/opt/mozilla/ (perhaps followed by some other places).
(2) There should be a sensible default name, e.g. siteprefs.cfg. At the moment
the administrator has to use the old complicated user preference scheme just to
enable the new simpler one.
(3) What on earth is the ROT13 business for? The default should be to accept a
plain text file (and maybe accept ROT13 for backward compatibility).

My comments are Unix-orientated; I guess Windows doesn't have an equivalent of
the /etc directory. But if these changes were made then most of section 2 could
be eliminated and replaced by something like

You need to put your site preferences in a file called siteprefs.cfg. On Unix
this file should be put in the directory /etc/opt/mozilla; on Windows put it in
the base of the Mozilla installation directory.

Bob