Nick McSpadden has posted some notes about using the Firefox CCK to manage Firefox 10 ESR here:
It grates on me that (since about version 8) any time a new version of Firefox is released, I get to choose between the following evils:
- Repackage Firefox.
- Run a script or install an auxiliary package after installing a new version of Firefox.
- Leave Firefox unmanaged.
This problem isn’t so bad if your machines are pretty tightly managed, but if your users can upgrade Firefox on their own or have figured out they can run Firefox from any location they have write access to, then Firefox is essentially unmanageable.
Previously, I have written on deploying Firefox extensions globally, and using the Firefox Client Customization Kit (CCK) to customize Firefox for your organization.
Using the CCK involves creating a Firefox extension, and most likely, you’ll want to deploy it globally. A few commenters on the CCK post were confused about the details around that, so this post is an attempt to clear all that up. Continue reading “Firefox global extensions, again”
I’m experimenting with a new (to me) method of delivering configuration settings for Firefox.
Previously I was inserting custom configuration files into the application bundle.
While this worked, it had a significant disadvantage. In order to be able to install new versions of Firefox without deleting these inserted files, I had to repackage new Firefox releases. This is very easy and takes little time, but is still more work than zero. I wanted to see if I could make things more modular, so I could install Firefox from the Mozilla disk image without having to repackage it.
Continue reading “More Firefox customization”