Yes mozilla should really release x86_64 linux builds. I find the easiest way to use Firefox 3.5 is to download the tarball from mozilla.com, untar it somewhere and then symlink the firefox binary to somewhere like ~/bin or /usr/local/bin. I've been using it for a long time this way.
|
Quote:
I stand corrected. I need an 64bit laptop ;) |
You know the build works for 32 and 64 bit right?
|
Quote:
Code:
cd ~/firefox/plugins Then cd up to ~/firefox. Then run: Code:
./firefox & You may want to backup your ~/.mozilla directory first in case you want to go back to FF 3.01x, although I don't think it would cause a problem either way. If it did cause problems you could just create a new profile. |
I compiled it yesterday on slamd64 and it works fine (using it now).
Quote:
|
Actually I don't care too much about this because I always follow the current and I believe it will be in current in a near future ;)
|
I have been using FF 3.5 for a few hours now. It is good, and has a few more features:
http://www.mozilla.com/en-US/firefox/3.5/releasenotes/ ... but imo there is no compelling reason to want or need FF 3.5. That is, unless you just can't wait to try it out ... like me! |
Quote:
A failing installation is offcourse not what you want to happen, but still, I'd rather reinstall FireFox than upgrade to SW 13.0.. most probably since SW13 aint available, and FF3.5 allready is :) The only things I now know I would like to have is KDE 4.x instead of 3.5, but that's worth the wait ( I guess/hope ) since it still only brings mostly eye candy,. and yes, a squeezy little more out-o-the-box support for wireless networks for my slacktop, since I had some trouble setting it up properly. |
Quote:
Regards, -Drew |
Using firefox's AutoUpdate feature on a Slackware firefox package will make a tiny mess. If you someday remove or upgrade the firefox package, all those new files that were put in the installation directory by the AutoUpdate will not be removed with the package. You will have to remove the old install directory manually.
It really is very very easy to just take the mozilla binary source and use the official mozilla-firefox slackBuild to make your own packages (no waiting for the official Slackware release). Then upgrade firefox properly. I modified the official slackBuild so that I don't have to modify the patches for differences in version numbers and so that I can have RSS feed integration and alternate desktop icons. All I have to do is run the slackBuild with the firefox version specified and I have a new package. upgradepkg the new package. done. |
Quote:
Are you willing to share your modified SlackBuild? Regards, -Drew |
Quote:
Note, I did not include the Firefox icon that I use. I use the blue one found at gnome-look.org. With this SlackBuild you should not have to modify it between version changes. Just run it as Code:
VERSION=3.5.xx ./mozilla-firefox.SlackBuild |
Probably not.. http://www.eweek.com/c/a/Enterprise-...5-Bugs-747510/
|
Quote:
|
As usual there are bugs ... it's inevitable ... but so far I haven't hit any :)
|
All times are GMT -5. The time now is 04:03 AM. |