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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hiya,
Just a quick question about web browsers really. I've got a script that updates my firefox, but i thought i'd look at the ones that come with slackware. Is there any reason why they're all out of date? I tried seamonkey amd konquerer (sorry for spelling), and i also downloaded and installed chromium via a slackbuild for 14.1 (which took a very long time), and that's out of date as well. i'm getting the feeling that i need scripts to run to update all browsers i want to try? By "out of date" i mean the first time i open the browser i get "this version is no longer supported".
Not trying to have a go or anything, i was just curious.
Are you aware of the patches/ directory on your favorite mirror? It contains update packages since the original release. On 14.1, seamonkey is at 2.39 (from its initial 2.21 version on 14.1), which is the latest from Mozilla. Firefox is at 38.7.0 (from its initial 24.1.0 version on 14.1), which is the patch level in that ESR (extended support release) version. As far as scripts, you should look into using slackpkg to keep your system up-to-date with the latest security patches Pat puts out.
As far as chromium, I'm assuming you grabbed the chromium slackbuild on SBo, however, since that one is outdated, the better one to use is Eric's (Alien Bob) script or package. He stays pretty up-to-date with those, and you can use his pre-compiled packages rather than compiling your own (which, as you noticed, can take a long time).
Thanks for the speedy reply.
Yep, i'm doing it all wrong I guess. I need to look at a patches folder somewhere?
I have always used slackpkg (update and then upgrade-all) to keep my system up to date, but i have not been aware of the patchs directory, so thanks for that. And I didn't know Eric had done chromium packages, I'll take a look at those too.
slackpkg will keep you up-to-date with the patches/ directory, so you may not have it configured correctly. Ensure you have a proper mirror uncommented and see if slackpkg pulls any additional updates. Also, verify you don't have the packages blacklisted.
the only package i have blacklisted is firefox as i get that manually with a script (i'm on v45 now).
i was looking here: http://slackware.uk/slackware/slackw...ches/packages/ and notice, like you said, that the latest sea monkey is 2.39. This is the version I have, and yet this is the version where the browser itself is telling me i'm using an "old stable version". Maybe that's not as worrying as it sounds then?
i was looking here: http://slackware.uk/slackware/slackw...ches/packages/ and notice, like you said, that the latest sea monkey is 2.39. This is the version I have, and yet this is the version where the browser itself is telling me i'm using an "old stable version". Maybe that's not as worrying as it sounds then?
I don't think it's the browser telling you it's out of date. It's more likely to be the website. Google sites have an annoying habit of doing that, most likely because they want to force everyone to use Chrome.
Apologies for my previous message, apparently seamonkey just released v2.40 on 10 MAR. If it is a security related update (possibly even if it isn't) it might be patched on 14.1 soon.
FYI the 2.40 tarball should build fine with the SlackBuild in /patches/source/seamonkey/ (I actually built in on current, haven't tried it on 14.1) so if anyone is in a hurry...
In case it helps, here's my Slackware update script, courtesy of one of the members of my LUG. For it to work, you must uncomment a mirror in /etc/slackpkg/mirrors:
If you have installed software from other sources, such as Slackbuilds.org or AlienBob's repos, you need to edit /etc/slackpkg/blacklist appropriately.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Rep:
Quote:
Originally Posted by bassmadrigal
Apologies for my previous message, apparently seamonkey just released v2.40 on 10 MAR. If it is a security related update (possibly even if it isn't) it might be patched on 14.1 soon.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.