I use and enjoy Firefox on my Ubuntu 10.04.2 laptop (although Firefox needs work for the Linux/Ubuntu version).
Yet I realize that in comparison to other pieces of software that have an "Ubuntu/Debian" version (.deb
file, and usually .rpm
files as well). I don't see it in one of the most profound assets of the FLOSS world.
The Question is - Why?
If Google Chrome/ium can , why can't they? It will be easier to get up-to-date software and features and so forth.
I think this question can only be definitely answered by some one from Mozilla. My guess is that they dont do it because they dont need to. When Ubuntu's Mozilla team is already doing a fantastic job why would Mozilla want to waste their resources re-doing the same? They are better off focusing on making Firefox better than packaging it for different platforms.
Why are you limiting your list to
.deb
and.rpm
? What about Gentoo ebuilds, Arch packages, Pardus PISI files, Slax' LZM files, PUP/PET of Puppy linux and whatnot?The sheer number of linux distributions and package managers out there is the reason: Nobody of Mozilla can test all of that.
What if I invent my own Linux distribution with its own package format? Do you expect Mozilla to support that, too? Even if I'm the only user? What if there are 10 users of my distribution? Where do you draw the line between supported and unsupported distribution?
What about dependencies? Firefox 14 might work with ffmpeg 12, but Debian ships ffmpeg 11.92. Fedora 23 ships ffmpeg 12.2. Mozilla cannot resolve all this issues.
This are the reasons why packaging for distributions is the task of the distribution people, not the application programmer's.
I think Mozilla doesn't want that... They only built the cross-platform browser, and help users use it easily, make all add-ons compatible over the different systems...
By the way, if Mozilla focus on building deb, rpm,... they must work more harder... For example, they need to create deb file that work on Ubuntu 11.04 (with Global menu, that only work on Unity), they must create deb file to work with GNOME theme... So, if they only provide tar file, users only need to untar it and run, and then users can choose another profile if they want, or easily run Debug mode (for addon developers)...
But, if you want deb file, you can follow that instruction: http://www.linuxquestions.org/questions/debian-26/how-to-build-a-deb-of-the-firefox-cvs-trunk-680801/. That is old, I know, but I think it maybe help you.