Firefox 3.5 coming out -- will it be in Slackware 13?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
If it ain't included, you could still install it later on? It's not so, that if it ain't in the release, it can't be installed later on?
Just download firefox 3.5 to your home directory and untar it. Then to get all your plugins working, symlink your /usr/lib/mozilla/plugins/* to firefox3.5 plugins directory:
Code:
cd ~/firefox/plugins
ln -s /usr/lib/mozilla/plugins* .
(That is a period "." at the end of that command.)
Then cd up to ~/firefox.
Then run:
Code:
./firefox &
And you will be running FF 3.5. This will not affect the FF that is currently installed in Slackware 12.2.
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:
Originally Posted by adriv
But that means that you're running FF as root, that's not a great idea (not much harm done if you only do that for upgrades, but don't do that by default).
If you run it as a user, the auto-upgrade mechanism won't work.
And even if you run it as root, it sometimes fails and then you still need to install it manually. ...
Actually I install FF to my home directory, not that it really matters for 64-bit because it can't auto-update anyway. But for 32-bit it could auto-update itself.
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!
But that means that you're running FF as root, that's not a great idea (not much harm done if you only do that for upgrades, but don't do that by default).
If you run it as a user, the auto-upgrade mechanism won't work.
And even if you run it as root, it sometimes fails and then you still need to install it manually. ...
As root yes. As the auto-upgrade function didn't work as normal user. But still: logging on as root isn't forbidden for administrative purposes as upgrading programs
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.
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.
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.
Shadowsnipes,
Are you willing to share your modified SlackBuild?
Most of the bugs will mostly likely be fixed within a couple of months. Regardless of whether or not it is released with Slackware 13, FF is an easy drop in package.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
