They have recently added this feature to their Seneca Fedora-Firefox repository and today I would like to share with you what getting updates on Fedora looks like.
Note that this is just a proof-of-concept and that they will (hopefully) continue dealing with all issues and get it integrated into our Mozilla systems and/or with Fedora's (suggestions/directions welcome!) in following quarters.
This post proves again that a well defined problem when given to Seneca's open-source students helps us move forward when we lack man-power. This is one of the first fruits out of the several MozillaReleng-Seneca projects.
The structure of the post will follow as:
- Getting the repository
- Install Minefield
- New update available
- What's next?
- Known issues or problems
First we have to make Fedora to know where to pull the package from.
This means that we have to add our "Firefox Nightly" repository to our list of Software Sources.
To do so download this rpm and install it: firefox-repo-0.3-2.noarch.rpm
Once installed you should be able to see the following screen shot when you do this:
- System -> Administration -> Software Sources
|Software Sources view with "Firefox Nightly" integrated into it|
Install Minefield (a.k.a. Firefox nightly build)
Now that the software source has been added we can decide to install the latest Firefox nightly.
To do so follow one of these two methods:
- System -> Administration -> Add/Remove Software
- Search for "Minefield"
- Check the latest build and select "Apply"
|Once installed, Fedora prompts you to run the application and it reminds you from where you can run the application|
- yum install minefield
- /usr/bin/minefield -> /usr/lib/minefield-4.0b8pre/firefox
- Add a Menu item under "Applications->Internet"
NOTE: I am not comfortable about where we unpack (/usr/lib/minefield-4.0b8pre) as I don't know what will happen when we bump the version.
New update available
How do I receive updates?
|Software Update window showing a "Mozilla Firefox Web Browser Nightly" update|
Let me know what your thoughts are or what we are doing wrong by:
- Adding a comment to this post.
- Adding a comment to Bug 600317.
- or you can email me directly armenzg [AT] mozilla.com
In case you wanted to have a look at the different files in the repository:
- we need to make sure that we are doing everything according to the guidelines that Fedora has for packaging and third party sources
- get people to test it and take input from Fedora/Linux veterans
- integrate it into Release Engineering systems
- does our setup work for other distributions using yum? if not, why not?
- set things up for more branches than just "mozilla-central"
- set things up for all locales
- set things up for betas
- define what the ideal world would look like
- Current and previous Minefield nightly show up under "Add/Remove Software"
- Setting Minefield as the default browser seems to mess up the "Preferred Web Browser" icon (I need to verify).
- Using the "Preferred Web Browser" launcher opens "file://home/armenzg/". Is it supposed to be like that?
- Should we be listed under "debug and development software sources" on the Software Sources manager?
- Minefield gets unpacked under /usr/lib/minefield-4.0b8pre. Should this be instead /usr/lib/minefield? (version agnostic)
- Minefield when launched from Applications->Internet->Minefield starts with the ProfileManager and allows running the nightly build with the other instances of Firefox ("minefield --no-remote --ProfileManager); should this not be a feature?
- Since /usr/lib/minefield-4.0b8 is owned by "root" Firefox's update system doesn't work. If we change ownership then updates work again and I wonder what bug would I hit if I can receive updates through yum and through AUS. Only one way to find out!
- I also believe that there is not a way to offer partial updates through yum as we do through our normal update system
This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.